# CVE-2011-4538: Information disclosure in n/a

> Attackers can obtain sensitive information by reading passwords within exported settings on Lexmark devices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2020
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v2r7-6rp8-j3j6

## What is CVE-2011-4538?

CVE-2011-4538 is a medium-severity vulnerability in n/a, published on 9 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lexmark X, W, T, E, and C devices before 2012-02-09 allow attackers to obtain sensitive information by reading passwords within exported settings.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2011-4538?

It affects 33 products.


Products: Lexmark C540 Firmware, Lexmark C543 Firmware, Lexmark C544 Firmware, Lexmark C546 Firmware, Lexmark C734 Firmware, Lexmark C736 Firmware, Lexmark E260 Firmware, Lexmark E360 Firmware, Lexmark E460 Firmware, Lexmark E462 Firmware, Lexmark T650 Firmware, Lexmark T652 Firmware, Lexmark T654 Firmware, Lexmark W850 Firmware, Lexmark X363 Firmware, Lexmark X364 Firmware, Lexmark X463 Firmware, Lexmark X464 Firmware, Lexmark X466 Firmware, Lexmark X543 Firmware and 13 more.

## How do I fix CVE-2011-4538?

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

## Is CVE-2011-4538 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4538 and fix it if it is affected.

What it is: CVE-2011-4538 is a medium-severity vulnerability in n/a, published on 9 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4538 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-2011-4538/ (Markdown: https://insights.sbomify.com/CVE-2011-4538/index.md)
```

## Sources

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

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