# CVE-2015-0452: Information disclosure in n/a

> Remote attackers can compromise confidentiality in Oracle VM Server for SPARC via unknown vectors in Ldom Manager.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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 stated
- **Fix available:** No
- **Published:** 16 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8864-xrrr-9569

## What is CVE-2015-0452?

CVE-2015-0452 is a medium-severity vulnerability in n/a, published on 16 Apr 2015. It can be exploited over the network.

### Official description

Unspecified vulnerability in the Oracle VM Server for SPARC component in Oracle Sun Systems Products Suite 3.1 and 3.2 allows remote attackers to affect confidentiality via unknown vectors related to Ldom Manager.

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

It affects 1 product.


Products: Oracle Vm Server.

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

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

## Is CVE-2015-0452 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-4480](https://insights.sbomify.com/CVE-2016-4480/): Privilege escalation in n/a (high 8.4)
- [CVE-2016-4962](https://insights.sbomify.com/CVE-2016-4962/): Privilege escalation in n/a (medium 6.7)
- [CVE-2017-3242](https://insights.sbomify.com/CVE-2017-3242/): Denial of service in LDOMS (medium 5.9)
- [CVE-2020-2571](https://insights.sbomify.com/CVE-2020-2571/): Missing authorization in LDOMS (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-0452 is a medium-severity vulnerability in n/a, published on 16 Apr 2015. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2015-0452 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-0452/ (Markdown: https://insights.sbomify.com/CVE-2015-0452/index.md)
```

## Sources

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

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