# CVE-2012-2668: Weak cryptography in n/a

> OpenLDAP with Mozilla NSS ignores configured cipher suites, potentially exposing sensitive data via weak encryption to remote attackers.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g25q-m772-8jx8, RHSA-2012:1151

## What is CVE-2012-2668?

CVE-2012-2668 is a medium-severity vulnerability in Openldap Openldap, published on 17 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libraries/libldap/tls_m.c in OpenLDAP, possibly 2.4.31 and earlier, when using the Mozilla NSS backend, always uses the default cipher suite even when TLSCipherSuite is set, which might cause OpenLDAP to use weaker ciphers than intended and make it easier for remote attackers to obtain sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2012-2668?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openldap` | Red Hat:enterprise_linux:6::client | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-clients` | Red Hat:enterprise_linux:6::client | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-servers` | Red Hat:enterprise_linux:6::client | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-servers-sql` | Red Hat:enterprise_linux:6::client | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-clients` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-servers` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-servers-sql` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap` | Red Hat:enterprise_linux:6::server | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-clients` | Red Hat:enterprise_linux:6::server | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-servers` | Red Hat:enterprise_linux:6::server | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-servers-sql` | Red Hat:enterprise_linux:6::server | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-clients` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-servers` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.4.23-26.el6_3.2 |
| `openldap-servers-sql` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.4.23-26.el6_3.2 |

Products: Openldap Openldap.

## How do I fix CVE-2012-2668?

Apply the vendor's patch.

## Is CVE-2012-2668 being exploited?

There is no known exploitation of CVE-2012-2668 in the wild and no public exploit code.

## Other vulnerabilities in Openldap Openldap

- [CVE-2015-3276](https://insights.sbomify.com/CVE-2015-3276/): Weak cryptography in n/a (high 7.5)
- [CVE-2002-1378](https://insights.sbomify.com/CVE-2002-1378/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1379](https://insights.sbomify.com/CVE-2002-1379/): Code injection in n/a (high 7.5)
- [CVE-2002-0045](https://insights.sbomify.com/CVE-2002-0045/): Missing authorization in n/a (high 7.5)
- [CVE-2005-4442](https://insights.sbomify.com/CVE-2005-4442/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2668 and fix it if it is affected.

What it is: CVE-2012-2668 is a medium-severity vulnerability in Openldap Openldap, published on 17 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2668 in the wild and no public exploit code.

Affected product: Openldap Openldap. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-2668/ (Markdown: https://insights.sbomify.com/CVE-2012-2668/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2668
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2668
- OSV: https://osv.dev/vulnerability/CVE-2012-2668

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-2668/
Summaries are generated and may contain mistakes; the official description above is the record.
