CVE-2019-1010316
UnknownEPSS 0.31%
Last modified
CVE-2019-1010316 is a vulnerability of currently unknown severity. pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control. The impact is: False locking impression when run in a non-X11 session. EPSS estimates a 0.31% chance of exploitation in the next 30 days.
Description
pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control. The impact is: False locking impression when run in a non-X11 session. The fixed version is: 0.4.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Pyxtrlock Project | Pyxtrlock | <= 0.3 |
References
- https://github.com/leonnnn/pyxtrlock/issues/21Issue Tracking, Third Party Advisory
- https://github.com/leonnnn/pyxtrlock/issues/21Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-1010316?
pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control. The impact is: False locking impression when run in a non-X11 session. The fixed version is: 0.4.
How severe is CVE-2019-1010316?
Severity scoring for CVE-2019-1010316 is pending analysis. The EPSS model estimates a 0.31% probability of exploitation in the next 30 days.
How do I fix CVE-2019-1010316?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2019-1010316?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
