Pyxdg
Vendor:
First CVE: Jan 28, 2014 · Active for 12 years
2
Total CVEs
More Total CVEs than 49% of tracked products
1.0
Avg CVEs / Year
Bottom 1%
5.4
Avg CVSS
Higher Avg CVSS than 11% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Pyxdg over time
Volume of CVEsAvg CVSS Base Score
First CVE
Jan 28, 2014
12 years ago
Most Recent CVE
Jun 6, 2019
2,605 days ago
CVE Severity & Scoring
Pyxdg2 CVEs
50%
50%
All CVEs352,231 CVEs
45%
40%
11%
LowHigh
Attack Vector
Local0 (0.0%)
Network1 (50.0%)
Unknown1 (50.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High1 (50.0%)
Unknown1 (50.0%)
User Interaction
None0 (0.0%)
Unknown1 (50.0%)
Required1 (50.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None1 (50.0%)
Unknown1 (50.0%)
Top CVEs
Signals from CVEs in this product scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2019-12761HIGH A code injection issue was discovered in PyXDG before 0.26 via crafted Python code in a Category element of a Menu XML document in a .menu file. XDG_CONFIG_DIRS must be set up to t | Jun 6, 2019 | 7.5 | 25 | NO | NO |
Race condition in the xdg.BaseDirectory.get_runtime_dir function in python-xdg 0.25 allows local users to overwrite arbitrary files by pre-creating /tmp/pyxdg-runtime-dir-fallback- | Jan 28, 2014 | 3.3 | 12 | 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 Pyxdg
Top CWEs
Versions
| Version | CVE Count | Avg CVSS | Avg EPSS | KEV | Exploits |
|---|---|---|---|---|---|
| 0.25 | 1 | 3.3 | 0.3% | 0 | 0 |