# CVE-2005-3472: Information disclosure in n/a

> Attackers can read sensitive configuration data from Sun Java System Communications Express, potentially exposing credentials or system details.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-44xc-2pmv-465w

## What is CVE-2005-3472?

CVE-2005-3472 is a medium-severity vulnerability in n/a, published on 3 Nov 2005. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in Sun Java System Communications Express 2005Q1 and 2004Q2 allows local and remote attackers to read sensitive information from configuration files.

## Which versions are affected by CVE-2005-3472?

It affects 1 product.


Products: Sun Java System Communications Express.

## How do I fix CVE-2005-3472?

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

## Is CVE-2005-3472 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4456](https://insights.sbomify.com/CVE-2010-4456/): Other in n/a (medium 4.3)
- [CVE-2010-1227](https://insights.sbomify.com/CVE-2010-1227/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-1729](https://insights.sbomify.com/CVE-2009-1729/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-0877](https://insights.sbomify.com/CVE-2009-0877/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3472 and fix it if it is affected.

What it is: CVE-2005-3472 is a medium-severity vulnerability in n/a, published on 3 Nov 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3472 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-2005-3472/ (Markdown: https://insights.sbomify.com/CVE-2005-3472/index.md)
```

## Sources

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

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