Various Lexmark products have Incorrect Access Control (issue 1 of 2).
- Published
- Aug 28, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 56th percentile
- CWE
- CWE-306
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| lexmark | cs31x firmware | cpe:2.3:o:lexmark:cs31x_firmware |
| lexmark | cs31x | cpe:2.3:h:lexmark:cs31x |
| lexmark | cs41x firmware | cpe:2.3:o:lexmark:cs41x_firmware |
| lexmark | cs41x | cpe:2.3:h:lexmark:cs41x |
| lexmark | cx310 firmware | cpe:2.3:o:lexmark:cx310_firmware |
| lexmark | cx310 | cpe:2.3:h:lexmark:cx310 |
| lexmark | ms310 firmware | cpe:2.3:o:lexmark:ms310_firmware |
| lexmark | ms310 | cpe:2.3:h:lexmark:ms310 |
| lexmark | ms312 firmware | cpe:2.3:o:lexmark:ms312_firmware |
| lexmark | ms312 | cpe:2.3:h:lexmark:ms312 |
| lexmark | ms317 firmware | cpe:2.3:o:lexmark:ms317_firmware |
| lexmark | ms317 | cpe:2.3:h:lexmark:ms317 |
and 38 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lexmark cs31x firmwareup to lw71.vyl.p229 inclusive
- lexmark cs41x firmwareup to lw71.vy2.p229 inclusive
- lexmark cx310 firmwareup to lw71.gm2.p229 inclusive
- lexmark m1140 firmwareup to lw71.prl.p229 inclusive
- lexmark m1145 firmwareup to lw71.pr2.p229 inclusive
- lexmark m3150dn firmwareup to lw71.pr2.p229 inclusive
- lexmark m5163dn firmwareup to lw71.dn2.p229 inclusive
- lexmark ms310 firmwareup to lw71.prl.p229 inclusive
- lexmark ms312 firmwareup to lw71.prl.p229 inclusive
- lexmark ms315 firmwareup to lw71.tl2.p229 inclusive
- lexmark ms317 firmwareup to lw71.prl.p229 inclusive
- lexmark ms410 firmwareup to lw71.prl.p229 inclusive
- lexmark ms415 firmwareup to lw71.tl2.p229 inclusive
- lexmark ms417 firmwareup to lw71.tl2.p229 inclusive
- lexmark ms51x firmwareup to lw71.pr2.p229 inclusive
- lexmark ms610dn firmwareup to lw71.pr2.p229 inclusive
- lexmark ms617 firmwareup to lw71.pr2.p229 inclusive
- lexmark ms71x firmwareup to lw71.dn2.p229 inclusive
- lexmark ms810 firmwareup to lw71.dn2.p229 inclusive
- lexmark ms811 firmwareup to lw71.dn2.p229 inclusive
Same product
lexmark: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-9933Various Lexmark products have a Buffer Overflow (issue 3 of 3).39Monitor
- CVE-2019-9932Various Lexmark products have a Buffer Overflow (issue 2 of 3).39Monitor
- CVE-2019-9930Various Lexmark products have an Integer Overflow.39Monitor
- CVE-2019-10058Various Lexmark products have Incorrect Access Control.36Monitor
- CVE-2019-9931Various Lexmark printers contain a denial of service vulnerability in the SNMP service that can be exploited to crash the device.30Monitor
- CVE-2019-10057Various Lexmark products have CSRF.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support teamapp.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) { app.post( "/maintenance/reset", requireSession, requireRole("admin"), resetDevice );}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.