dbcve.org
Iprint\&scanApplication · Brother

CVE-2023-51654

MEDIUM · 5.5 CVSS v3.1 Published 2023-12-26
Fix available
A fix is available. Upgrade to after 11.0.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improper link resolution before file access ('Link Following') issue exists in iPrint&Scan Desktop for Windows versions 11.0.0 and earlier. A symlink attack by a malicious user may cause a Denial-of-service (DoS) condition on the PC.

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 confidence

iPrint&Scan Desktop for Windows versions 11.0.0 and earlier contains a link following (symlink) vulnerability where the application improperly resolves symbolic links before file access. A local malicious user can create a specially crafted symlink to trigger the application into following it, causing a denial-of-service condition on the affected PC.

MitigationApply the vendor-supplied patch or upgrade to a version newer than 11.0.0 when released. Until then, restrict physical access and local user privileges to prevent symlink creation attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Iprint\&scanApplication
Affected:<= 11.0.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Brother iPrint&Scan is installed
    Open Windows Settings > Apps > Apps & features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs
    Affected if Brother iPrint&Scan or Brother iPrint&Scan Desktop appears in the installed programs list
  2. Determine the installed version
    Right-click the iPrint&Scan application in the Start menu and select Properties, or check the version in Programs and Features. The version is typically displayed as DisplayVersion in the registry key for the application
    Affected if The version shown is 11.0.0 or any version lower than 11.0.0 (for example, 10.x, 9.x, etc.)
  3. Confirm the application is the vulnerable Windows desktop version
    Verify the installed application is iPrint&Scan Desktop for Windows and not a mobile or web version. Check the program directory under C:\Program Files\Brother\iPrintScan or C:\Program Files (x86)\Brother\iPrintScan if it exists
    Affected if The iPrint&Scan Desktop application is found in the Program Files directories with version 11.0.0 or earlier
  4. Check for exploitable symlink conditions
    Review file and folder permissions on the application data directories. If regular users can create files or symlinks in directories used by iPrint&Scan, the vulnerability may be exploitable. Run 'icacls "C:\ProgramData\Brother\iPrintScan"' or similar paths to inspect permissions
    Affected if Non-privileged users have write permissions to application directories where symlinks could be planted

You are affected if Brother iPrint&Scan Desktop for Windows version 11.0.0 or earlier is installed and running on your system, particularly if users with limited privileges can create symlinks in application directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 11.0.0
Interim mitigation

Apply the vendor-supplied patch or upgrade to a version newer than 11.0.0 when released. Until then, restrict physical access and local user privileges to prevent symlink creation attacks.

Recommended fix Moderate confidence

Latest version after 11.0.0 (check vendor for current release)

  1. 1. Identify the current installed version of iPrint&Scan Desktop for Windows by opening the application and checking 'Help' > 'About' or checking 'Programs and Features' in the Control Panel.
  2. 2. Navigate to the official Brother support website (brother.com) or the vendor's download page for iPrint&Scan.
  3. 3. Download the latest available version of iPrint&Scan Desktop for Windows.
  4. 4. Uninstall the current version through Windows 'Programs and Features' or 'Apps & features'.
  5. 5. Restart the computer to ensure all processes are cleared.
  6. 6. Install the newly downloaded version of iPrint&Scan Desktop for Windows.
  7. 7. Verify the installation was successful and confirm the new version number matches the downloaded release.
Caveat Review release notes for any functionality changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iprint\&scan Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51654 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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