# CVE-2019-6489: Missing authorization in n/a

> Remote attackers can erase stored shortcuts on Lexmark multifunction printers due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 11 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9v6m-jhh9-pq68

## What is CVE-2019-6489?

CVE-2019-6489 is a medium-severity missing authorization vulnerability in n/a, published on 11 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain Lexmark CX, MX, X, XC, XM, XS, and 6500e devices before 2019-02-11 allow remote attackers to erase stored shortcuts.

## Which versions are affected by CVE-2019-6489?

It affects 40 products.


Products: Lexmark 6500e Firmware, Lexmark Cx310 Firmware, Lexmark Cx410 Firmware, Lexmark Cx510 Firmware, Lexmark Mx31x Firmware, Lexmark Mx410 Firmware, Lexmark Mx510 Firmware, Lexmark Mx511 Firmware, Lexmark Mx610 Firmware, Lexmark Mx611 Firmware, Lexmark Mx6500e Firmware, Lexmark Mx71x Firmware, Lexmark Mx81x Firmware, Lexmark Mx91x Firmware, Lexmark X46x Firmware, Lexmark X548 Firmware, Lexmark X65x Firmware, Lexmark X73x Firmware, Lexmark X74x Firmware, Lexmark X792 Firmware and 20 more.

## How do I fix CVE-2019-6489?

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

## Is CVE-2019-6489 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-44734](https://insights.sbomify.com/CVE-2021-44734/): Code injection in n/a (critical 9.8)
- [CVE-2021-44738](https://insights.sbomify.com/CVE-2021-44738/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-9930](https://insights.sbomify.com/CVE-2019-9930/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-9932](https://insights.sbomify.com/CVE-2019-9932/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-9933](https://insights.sbomify.com/CVE-2019-9933/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6489 and fix it if it is affected.

What it is: CVE-2019-6489 is a medium-severity missing authorization vulnerability in n/a, published on 11 Feb 2019. 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-2019-6489 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-2019-6489/ (Markdown: https://insights.sbomify.com/CVE-2019-6489/index.md)
```

## Sources

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

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