# CVE-2007-3700: Information disclosure in n/a

> Local attackers can read cleartext passwords from debug logs when debug level is enabled, leading to privilege escalation.

- **Severity:** Low 1.7 (`AV:L/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mm2x-5hh8-297w

## What is CVE-2007-3700?

CVE-2007-3700 is a low-severity vulnerability in n/a, published on 11 Jul 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sun Java System Access Manager (formerly Java System Identity Server) before 20070710, when the message debug level is configured in the com.iplanet.services.debug.level property in AMConfig.properties, logs cleartext login passwords, which allows local users to gain privileges by reading /var/opt/SUNWam/debug/amAuth.

## Which versions are affected by CVE-2007-3700?

It affects 1 product.


Products: Sun Java System Access Manager.

## How do I fix CVE-2007-3700?

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

## Is CVE-2007-3700 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2705](https://insights.sbomify.com/CVE-2008-2705/): Auth bypass in n/a (critical 9.3)
- [CVE-2009-0169](https://insights.sbomify.com/CVE-2009-0169/): Privilege escalation in n/a (critical 9.0)
- [CVE-2008-2945](https://insights.sbomify.com/CVE-2008-2945/): Code injection in n/a (high 7.5)
- [CVE-2007-5152](https://insights.sbomify.com/CVE-2007-5152/): Auth bypass in n/a (high 7.5)
- [CVE-2006-0531](https://insights.sbomify.com/CVE-2006-0531/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3700 and fix it if it is affected.

What it is: CVE-2007-3700 is a low-severity vulnerability in n/a, published on 11 Jul 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3700 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-2007-3700/ (Markdown: https://insights.sbomify.com/CVE-2007-3700/index.md)
```

## Sources

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

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