Credential compromise via account-lockout bypass
Published Jan 23, 2023 · Updated Apr 2, 2025
Authentication lockout bypass in Lexmark device firmware allows remote attackers to guess local-account credentials without attempt limits. The local-account lockout control fails to enforce the configured failed-attempt threshold and lockout interval, permitting unrestricted credential guesses. The affected device must expose its login interface, and successful guessing compromises credentials for the targeted local account.
Summary
What happened
Authentication lockout bypass in Lexmark device firmware allows remote attackers to guess local-account credentials without attempt limits. The local-account lockout control fails to enforce the configured failed-attempt threshold and lockout interval, permitting unrestricted credential guesses. The affected device must expose its login interface, and successful guessing compromises credentials for the targeted local account.
The record
- CVE
- CVE-2023-22960
- Published
- Jan 23, 2023
- Updated
- Apr 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-307, CWE-799, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2023CVE publishedPublication date reported by the CVE source.
- Apr 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo