Pyxtrlock
Vendor:
First CVE: May 19, 2014 · Active for 12 years
2
Total CVEs
More Total CVEs than 49% of tracked products
2.0
Avg CVEs / Year
Higher CVE frequency than 60% of tracked products
2.9
Avg CVSS
Bottom 1%
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Pyxtrlock over time
Volume of CVEsAvg CVSS Base Score
First CVE
May 19, 2014
12 years ago
Most Recent CVE
May 19, 2014
4,452 days ago
CVE Severity & Scoring
Pyxtrlock2 CVEs
100%
All CVEs352,785 CVEs
45%
40%
11%
Low
Attack Vector
Local0 (0.0%)
Network0 (0.0%)
Unknown2 (100.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High0 (0.0%)
Unknown2 (100.0%)
User Interaction
None0 (0.0%)
Unknown2 (100.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None0 (0.0%)
Unknown2 (100.0%)
Top CVEs
Signals from CVEs in this product scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
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 trigg | May 19, 2014 | 3.6 | 13 | NO | NO |
pyxtrlock before 0.2 does not properly check the return values of the (1) xcb_grab_pointer and (2) xcb_grab_keyboard XCB library functions, which allows physically proximate attack | May 19, 2014 | 2.1 | 11 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (2 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (2 CVEs).
Media Mentions
Signals from CVEs in this product scope (2 CVEs).
Top CNAs Publishing CVEs For Pyxtrlock
Top CWEs
Versions
| Version | CVE Count | Avg CVSS | Avg EPSS | KEV | Exploits |
|---|---|---|---|---|---|
| 0.1 | 1 | 2.1 | 0.4% | 0 | 0 |