dbcve.org
25xxnHardware / appliance · Lexmark

CVE-2013-6032

HIGH · 10.0 CVSS v2.0 Published 2014-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
cgi-bin/postpf/cgi-bin/dynamic/config/config.html on Lexmark X94x before LC.BR.P142, X85x through LC4.BE.P487, X644 and X646 before LC2.MC.P374, X642 through LC2.MB.P318, W840 through LS.HA.P252, T64x before LS.ST.P344, X64xef through LC2.TI.P325, C935dn through LC.JO.P091, C920 through LS.TA.P152, C78x through LC.IO.P187, X78x through LC2.IO.P335, C77x through LC.CM.P052, X772 through LC2.TR.P291, C53x through LS.SW.P069, C52x through LS.FA.P150, 25xxN through LCL.CU.P114, N4000 through LC.MD.P119, N4050e through GO.GO.N206, N70xxe through LC.CO.N309, E450 through LM.SZ.P124, E350 through LE.PH.P129, and E250 through LE.PM.P126 printers allows remote attackers to remove the Password Protect administrative password via the vac.255.GENPASSWORD parameter.

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 · high confidence

Multiple Lexmark printer models contain a vulnerability in the web interface CGI script (cgi-bin/postpf/cgi-bin/dynamic/config/config.html) that allows remote attackers to remove the Password Protect administrative password by manipulating the vac.255.GENPASSWORD parameter. This authentication bypass grants unauthorized administrative access to the printer's configuration.

MitigationApply the vendor-supplied firmware patches (e.g., LC.BR.P142 for X94x series) to all affected devices. If patching is not immediately feasible, restrict network access to the printer web interface to minimize exposure.

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
25xxnHardware / appliance
Affected:<= lcl.cu.p114
C52xHardware / appliance
Affected:<= ls.fa.p150
C53xHardware / appliance
Affected:<= ls.sw.p069
C77xHardware / appliance
Affected:<= lc.cm.p052
C78xHardware / appliance
Affected:<= lc.io.p187
C920Hardware / appliance
Affected:<= ls.ta.p152
C935dnHardware / appliance
Affected:<= lc.jo.p091
E250Hardware / appliance
Affected:<= le.pm.p126

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Identify the Lexmark printer model
    Access the printer's web interface and locate the model number in the main page or status section, or query the device via SNMP using: snmpwalk -v2c -c public <IP> sysDescr
    Affected if Model is one of: 25xxn, C52x, C53x, C77x, C78x, C920, C935dn, or E250
  2. Check the installed firmware version
    In the printer web interface, navigate to Settings > Firmware or About page to find the firmware version. Alternatively, use SNMP: snmpget -v2c -c public <IP> 1.3.6.1.2.1.43.5.1.1.14.1
    Affected if Firmware version is at or below: lcl.cu.p114 (25xxn), ls.fa.p150 (C52x), ls.sw.p069 (C53x), lc.cm.p052 (C77x), lc.io.p187 (C78x), ls.ta.p152 (C920), lc.jo.p091 (C935dn), or le.pm.p126 (E250)
  3. Verify the vulnerable CGI endpoint is accessible
    Attempt to access the vulnerable URL path: http://<PRINTER_IP>/cgi-bin/postpf/cgi-bin/dynamic/config/config.html - the page loads if the web interface is enabled
    Affected if The web interface and the config.html endpoint respond successfully, indicating the vulnerable script is available
  4. Check if password protection is currently applied
    In the printer web interface, navigate to Settings > Security > Password Protect or similar admin security settings to verify if administrative password protection is enabled
    Affected if Password protection is enabled and the device firmware version falls within the affected ranges, the device is vulnerable to having this protection removed via the documented parameter manipulation

The device is affected if it is one of the listed Lexmark models running firmware at or below the specified version thresholds and has its web interface accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware patches (e.g., LC.BR.P142 for X94x series) to all affected devices. If patching is not immediately feasible, restrict network access to the printer web interface to minimize exposure.

Fix this in 25xxn Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-6032 — 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-2013-6032 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