# CVE-2018-12049: Auth bypass in n/a

> Remote attackers can bypass authentication on Canon LBP6030w printers to gain full administrative access if default settings are retained.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jjcg-hp49-5xxw

## What is CVE-2018-12049?

CVE-2018-12049 is a critical authentication bypass vulnerability in n/a, published on 8 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote attacker can bypass the System Manager Mode on the Canon LBP6030w web interface without a PIN for /checkLogin.cgi via vectors involving /portal_top.html to get full access to the device. NOTE: the vendor reportedly responded that this issue occurs when a customer keeps the default settings without using the countermeasures and best practices shown in the documentation

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-12049?

It affects 1 product.


Products: Canon Lbp6030w Firmware.

## How do I fix CVE-2018-12049?

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

## Is CVE-2018-12049 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12049 and fix it if it is affected.

What it is: CVE-2018-12049 is a critical authentication bypass vulnerability in n/a, published on 8 Jun 2018. 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-2018-12049 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-2018-12049/ (Markdown: https://insights.sbomify.com/CVE-2018-12049/index.md)
```

## Sources

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

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