# CVE-2017-7588: Auth bypass in n/a

> Attackers can bypass authentication on Brother printers by using a valid AuthCookie returned during failed login attempts.

- **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:** 12 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p9g5-cmfc-4v42

## What is CVE-2017-7588?

CVE-2017-7588 is a critical authentication bypass vulnerability in n/a, published on 12 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On certain Brother devices, authorization is mishandled by including a valid AuthCookie cookie in the HTTP response to a failed login attempt. Affected models are: MFC-J6973CDW MFC-J4420DW MFC-8710DW MFC-J4620DW MFC-L8850CDW MFC-J3720 MFC-J6520DW MFC-L2740DW MFC-J5910DW MFC-J6920DW MFC-L2700DW MFC-9130CW MFC-9330CDW MFC-9340CDW MFC-J5620DW MFC-J6720DW MFC-L8600CDW MFC-L9550CDW MFC-L2720DW DCP-L2540DW DCP-L2520DW HL-3140CW HL-3170CDW HL-3180CDW HL-L8350CDW HL-L2380DW ADS-2500W ADS-1000W ADS-1500W.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-7588?

It affects 4 products.


Products: Brother Ads Firmware, Brother Dcp Firmware, Brother Hl Firmware, Brother Mfc Firmware.

## How do I fix CVE-2017-7588?

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

## Is CVE-2017-7588 being exploited?

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

Public exploit code:

- Brother MFC-J6520DW - Authentication Bypass / Password Change (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7588 and fix it if it is affected.

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

## Sources

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

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