parse_uri
glance/store/swift.py
Last patched
Overview
parse_uri in openstack/glance was changed by 1 published CVE fixes in 2013, in 3 distinct patches that added or removed 7 lines in total.
openstack/glance has 13 CVEs with a located fix in total, so 8% of them touched this function.
CVEs that patched it
Every published CVE whose fix changed parse_uri, newest first, with the lines each fix touched.
CVE-2013-0212 · lines 139–183 · +3 −4 in 3 hunks
Medium · CVSS 4.0EPSS 3.0%2013-02-24
Get an alert when the next CVE fix lands in openstack/glance, with the patched functions.
Monitor glance CVEsOther functions in these files
Functions in the same file that CVE fixes also changed.
Other hotspots in the repository
Functions in openstack/glance changed by the most CVE fixes.
Frequently asked questions
Common questions about CVE fixes to parse_uri.
- How many CVEs have patched parse_uri?
- 1 published CVEs changed parse_uri in openstack/glance, in 3 distinct patches totalling 7 changed lines, between 2013 and 2013.
- What is the latest CVE that changed parse_uri?
- CVE-2013-0212 (OpenStack Glance logs user name and password in cleartext), published 2013-02-24, changed lines 139 to 183 of glance/store/swift.py.
- How does parse_uri compare to the rest of openstack/glance?
- openstack/glance has 13 CVEs with a located fix in total; 1 of them changed parse_uri.
- What do the line numbers refer to?
- Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.
References
- glance/store/swift.py on GitHub (opens in a new tab)
- All patched functions in openstack/glance
- Patched functions directory
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Track openstack/glance CVEs
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.