Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-29155 is a critical-severity SQL Injection (CWE-89) vulnerability in Debian Debian Linux. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2022-29155 is a SQL injection vulnerability in the experimental back-sql backend of OpenLDAP slapd, affecting versions 2.x prior to 2.5.12 and 2.6.x prior to 2.6.2. The flaw arises from insufficient escaping of LDAP search filters, allowing a SQL statement to be injected during query processing and executed against the backend database.
An unauthenticated remote attacker can exploit the issue over the network by submitting a crafted LDAP search operation. Successful exploitation can result in full compromise of the confidentiality, integrity, and availability of the underlying data, consistent with the CVSS 9.8 rating and CWE-89 classification.
Advisories from Debian, NetApp, and OpenLDAP project references indicate that the issue is resolved by upgrading to the fixed releases 2.5.12 or 2.6.2, with corresponding package updates distributed through operating-system security channels.
The EPSS score rose from a low baseline to a peak of 0.2341, indicating that exploitation interest emerged after public disclosure and that the vulnerability warrants renewed attention.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-33563
Vulnerability Data
In OpenLDAP 2.x before 2.5.12 and 2.6.x before 2.6.2, a SQL injection vulnerability exists in the experimental back-sql backend to slapd, via a SQL statement within an LDAP query. This can occur during an LDAP search operation when the search…
more
filter is processed, due to a lack of proper escaping.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation and escaping of untrusted input such as LDAP search filters before they are used to construct SQL statements in the back-sql backend.
Mandates prompt application of vendor patches that correct the missing escaping logic, upgrading OpenLDAP to 2.5.12 or 2.6.2.
Requires disabling non-essential or experimental components such as the back-sql backend when it is not required, eliminating the vulnerable code path.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.