# CVE-2010-1558: Information disclosure in n/a

> Local attackers can bypass restrictions on the Send to e-mail feature to obtain sensitive information from HP MFP devices.

- **Severity:** Medium 4.7 (`AV:L/AC:M/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-74jq-7fr5-52q4

## What is CVE-2010-1558?

CVE-2010-1558 is a medium-severity vulnerability in n/a, published on 14 May 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in HP Multifunction Peripheral (MFP) Digital Sending Software before 4.18.3 allows local users to bypass intended restrictions on the MFP "Send to e-mail" feature, and obtain sensitive information, via unknown vectors.

## Which versions are affected by CVE-2010-1558?

It affects 1 product.


Products: Hp Multifunction Peripheral Digital Sending Software.

## How do I fix CVE-2010-1558?

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

## Is CVE-2010-1558 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0279](https://insights.sbomify.com/CVE-2011-0279/): Auth bypass in n/a (low 2.1)
- [CVE-2011-3163](https://insights.sbomify.com/CVE-2011-3163/): Information disclosure in n/a (low 1.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1558 and fix it if it is affected.

What it is: CVE-2010-1558 is a medium-severity vulnerability in n/a, published on 14 May 2010. 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-2010-1558 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-2010-1558/ (Markdown: https://insights.sbomify.com/CVE-2010-1558/index.md)
```

## Sources

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

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