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

> Remote attackers can view sensitive configuration data by canceling the authentication dialog on specific sub-pages of the switch interface.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mpjm-vcr7-5x83

## What is CVE-2007-3012?

CVE-2007-3012 is a medium-severity vulnerability in n/a, published on 5 Jul 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The web interface in Fujitsu-Siemens Computers PRIMERGY BX300 Switch Blade allows remote attackers to obtain sensitive information by canceling the authentication dialog when accessing a sub-page, which still displays the form field contents of the sub-page, as demonstrated using (1) config/ip_management.htm and (2) config/snmp_config.htm.

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

It affects 1 product.


Products: Fujitsu Primergy Bx300.

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

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

## Is CVE-2007-3012 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3012 is a medium-severity vulnerability in n/a, published on 5 Jul 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-3012 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-3012/ (Markdown: https://insights.sbomify.com/CVE-2007-3012/index.md)
```

## Sources

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

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