# CVE-2015-3230: Security feature bypass in n/a > Remote attackers can bypass SSL cipher restrictions in 389 Directory Server by requesting disabled ciphers, potentially weakening encryption security. - **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Oct 2015 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2015-3230, GHSA-2q4h-358c-9wqx, MGASA-2015-0402, RHBA-2015:1554, UBUNTU-CVE-2015-3230 ## What is CVE-2015-3230? CVE-2015-3230 is a high-severity vulnerability in n/a, published on 29 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 389 Directory Server (formerly Fedora Directory Server) before 1.3.3.12 does not enforce the nsSSL3Ciphers preference when creating an sslSocket, which allows remote attackers to have unspecified impact by requesting to use a disabled cipher. Weakness: CWE-254 ## Which versions are affected by CVE-2015-3230? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `389-ds-base` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.3.1-20.ael7b_1 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.3.1-20.ael7b_1 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.3.1-20.ael7b_1 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.3.1-20.ael7b_1 | | `389-ds-base` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.3.3.1-20.el7_1 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.3.3.1-20.el7_1 | Products: Fedoraproject 389 Directory Server. ## How do I fix CVE-2015-3230? Upgrade to a fixed version. ## Is CVE-2015-3230 being exploited? There is no known exploitation of CVE-2015-3230 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2017-7551](https://insights.sbomify.com/CVE-2017-7551/): Information disclosure in 389-ds-base (critical 9.8) - [CVE-2017-15135](https://insights.sbomify.com/CVE-2017-15135/): Auth bypass in 389-ds-base (high 8.1) - [CVE-2019-10171](https://insights.sbomify.com/CVE-2019-10171/): Denial of service in 389-ds-base (high 7.5) - [CVE-2018-14638](https://insights.sbomify.com/CVE-2018-14638/): Denial of service in 389-ds-base (high 7.5) - [CVE-2018-1054](https://insights.sbomify.com/CVE-2018-1054/): Denial of service in 389-ds-base (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2015-3230 and fix it if it is affected. What it is: CVE-2015-3230 is a high-severity vulnerability in n/a, published on 29 Oct 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-3230 in the wild and no public exploit code. Affected product: n/a. 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-3230/ (Markdown: https://insights.sbomify.com/CVE-2015-3230/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2015-3230 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-3230 - OSV: https://osv.dev/vulnerability/CVE-2015-3230 --- From sbomify Insights: https://insights.sbomify.com/CVE-2015-3230/ Summaries are generated and may contain mistakes; the official description above is the record.