Pyxml
Vendor:
First CVE: Nov 3, 2009 · Active for 16 years
2
Total CVEs
More Total CVEs than 49% of tracked products
1.0
Avg CVEs / Year
Bottom 1%
6.3
Avg CVSS
Higher Avg CVSS than 25% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Pyxml over time
Volume of CVEsAvg CVSS Base Score
First CVE
Nov 3, 2009
16 years ago
Most Recent CVE
Nov 22, 2019
2,436 days ago
CVE Severity & Scoring
Pyxml2 CVEs
50%
50%
All CVEs352,231 CVEs
45%
40%
11%
MediumHigh
Attack Vector
Local0 (0.0%)
Network1 (50.0%)
Unknown1 (50.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (50.0%)
High0 (0.0%)
Unknown1 (50.0%)
User Interaction
None1 (50.0%)
Unknown1 (50.0%)
Required0 (0.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-2009-3720MEDIUM The updatePosition function in lib/xmltok_impl.c in libexpat in Expat 2.0.1, as used in Python, PyXML, w3c-libwww, and other software, allows context-dependent attackers to cause a | Nov 3, 2009 | 5.0 | 35 | NO | NO |
CVE-2012-0877HIGH PyXML: Hash table collisions CPU usage Denial of Service | Nov 22, 2019 | 7.5 | 24 | 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 Pyxml
Top CWEs
Versions
No cataloged versions.