CVE-2024-22475
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site request forgery vulnerability in multiple printers and scanners which implement Web Based Management provided by BROTHER INDUSTRIES, LTD. allows a remote unauthenticated attacker to perform unintended operations on the affected product. As for the details of affected product names, model numbers, and versions, refer to the information provided by the respective vendors listed under [References].
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCSRF vulnerability in Brother printer/scanner Web Based Management interfaces allows remote unauthenticated attackers to trick authenticated administrators into performing unintended operations via malicious web requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Web Based Management is enabledAccess the printer control panel or admin settings menu. Look for Web Based Management or WBM setting under Network, Server, or Admin settings. If accessible via web browser, try navigating to the device IP address (http://[device IP]) to see if a login page appears.Affected if Web Based Management interface is turned ON and accessible via browser
-
Check device network accessibilityAttempt to reach the Web Based Management interface from a remote host using curl or a browser: curl -I http://[printer-ip]/ or https://[printer-ip]/. Also verify whether the device is NAT'ed or firewall-protected from untrusted networks.Affected if The WBM interface is reachable from network segments beyond the trusted local admin workstation
-
Verify administrative access statusLog into Web Based Management as administrator or check if persistent admin sessions are active. Review session management settings if available in the WBM interface under Network or Admin tabs.Affected if Administrative credentials are configured and WBM is accessible, creating potential for session hijacking via CSRF
-
Identify device model and firmware versionIn Web Based Management, navigate to General or Information pages to view the model name and firmware version. Alternatively, print a configuration or status page from the device control panel to retrieve firmware version.Affected if Firmware version cannot be verified or is older than vendor patches (contact vendor for specific version guidance)
-
Confirm CSRF protection status (if configurable)In Web Based Management, search for Security, CSRF, or Token settings under Admin or Network menus. Check if the interface implements anti-CSRF tokens for state-changing operations.Affected if No CSRF token or protection mechanism is visible in the WBM configuration
User is affected if Web Based Management is enabled and accessible over the network where untrusted parties could trick an authenticated administrator into clicking malicious requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied firmware updates when available; disable Web Based Management if unused; implement CSRF tokens in custom web applications interfacing with affected devices.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data