# CVE-2015-1816: Weak cryptography in n/a

> Man-in-the-middle attackers can spoof LDAP servers because the Forman library fails to verify SSL certificates during connections.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 14 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gjcw-j8fh-6j22

## What is CVE-2015-1816?

CVE-2015-1816 is a medium-severity vulnerability in Theforeman Foreman, published on 14 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Forman before 1.7.4 does not verify SSL certificates for LDAP connections, which allows man-in-the-middle attackers to spoof LDAP servers via a crafted certificate.

Weakness: CWE-310

## Which versions are affected by CVE-2015-1816?

It affects 1 product.


Products: Theforeman Foreman.

## How do I fix CVE-2015-1816?

Upgrade to a fixed version.

## Is CVE-2015-1816 being exploited?

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

## Other vulnerabilities in Theforeman Foreman

- [CVE-2018-14643](https://insights.sbomify.com/CVE-2018-14643/): smart_proxy_dynflow gem authentication bypass in Foreman remote execution feature (critical 9.8)
- [CVE-2017-7505](https://insights.sbomify.com/CVE-2017-7505/): Missing authorization in foreman (high 8.8)
- [CVE-2016-4475](https://insights.sbomify.com/CVE-2016-4475/): Missing authorization in n/a (high 8.8)
- [CVE-2016-3728](https://insights.sbomify.com/CVE-2016-3728/): Code injection in n/a (high 8.8)
- [CVE-2015-5246](https://insights.sbomify.com/CVE-2015-5246/): Auth bypass in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1816 and fix it if it is affected.

What it is: CVE-2015-1816 is a medium-severity vulnerability in Theforeman Foreman, published on 14 Aug 2015. 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-2015-1816 in the wild and no public exploit code.

Affected product: Theforeman Foreman. 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-2015-1816/ (Markdown: https://insights.sbomify.com/CVE-2015-1816/index.md)
```

## Sources

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

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