# CVE-2008-1995: Auth bypass in n/a

> Remote attackers can bypass access restrictions in Sun Java System Directory Proxy Server by exploiting incorrect policy application during connection classification.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6rhq-jp74-wpph

## What is CVE-2008-1995?

CVE-2008-1995 is a high-severity authentication bypass vulnerability in n/a, published on 28 Apr 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sun Java System Directory Proxy Server 6.0, 6.1, and 6.2 classifies a connection using the "bind-dn" criteria, which can cause an incorrect application of policy and allows remote attackers to bypass intended access restrictions for the server.

Weakness: CWE-264

## Which versions are affected by CVE-2008-1995?

It affects 1 product.


Products: Sun Java System Directory Server.

## How do I fix CVE-2008-1995?

No fix has been published for CVE-2008-1995 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-1995 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0609](https://insights.sbomify.com/CVE-2009-0609/): Denial of service in n/a (high 7.8)
- [CVE-2009-0576](https://insights.sbomify.com/CVE-2009-0576/): Denial of service in n/a (high 7.8)
- [CVE-2007-2466](https://insights.sbomify.com/CVE-2007-2466/): Denial of service in n/a (high 7.8)
- [CVE-2006-4175](https://insights.sbomify.com/CVE-2006-4175/): Denial of service in n/a (high 7.8)
- [CVE-2006-2513](https://insights.sbomify.com/CVE-2006-2513/): Privilege escalation in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1995 and fix it if it is affected.

What it is: CVE-2008-1995 is a high-severity authentication bypass vulnerability in n/a, published on 28 Apr 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1995 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-2008-1995/ (Markdown: https://insights.sbomify.com/CVE-2008-1995/index.md)
```

## Sources

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

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