CVE-2013-4426
What it is
pyxtrlock before 0.1 uses an incorrect variable name, which allows physically proximate attackers to bypass the lock screen via multiple failed authentication attempts, which trigger a crash.
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in. Limited direct impact.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 3.6 LOW (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Record status
- Modified
Affected
- Leon Weber Pyxtrlock ≤ 0.1
Attack profile CVSS 2.0 · 3.6
- Attack vector
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- Partial
Raw vector
AV:L/AC:L/Au:N/C:P/I:N/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2013-4426.md and follow it. Check whether this project is affected by CVE-2013-4426. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
