How many CVEs have patched _assign_unique_id?

2 published CVEs changed _assign_unique_id in openstack/keystone, in 2 distinct patches totalling 86 changed lines, between 2020 and 2020.

What is the latest CVE that changed _assign_unique_id?

CVE-2020-12689 (OpenStack Keystone EC2 and/or credential endpoints are not protected from a scoped context), published 2020-05-06, changed lines 63 to 97 of keystone/api/credentials.py.

How does _assign_unique_id compare to the rest of openstack/keystone?

openstack/keystone has 29 CVEs with a located fix in total; 2 of them changed _assign_unique_id.

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.

RadicalNotion.AI

Log in Create an account

openstack/keystone

Function

_assign_unique_id

Name: _assign_unique_id in openstack/keystone: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

keystone/api/credentials.py

Last patched May 6, 2020

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

86

Lines changed

Added plus removed

2020

Years

By CVE publication date

Overview

_assign_unique_id in openstack/keystone was changed by 2 published CVE fixes in 2020, in 2 distinct patches that added or removed 86 lines in total.

openstack/keystone has 29 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _assign_unique_id, newest first, with the lines each fix touched.

OpenStack Keystone EC2 and/or credential endpoints are not protected from a scoped context
CVE-2020-12689 · lines 63–97 · +27 −16
High · CVSS 8.7
EPSS 1.6%2020-05-06
OpenStack Keystone V3 /credentials endpoint policy logic allows to change credentials owner or target project ID
CVE-2020-12691 · lines 64–98 · +27 −16
High · CVSS 8.7
EPSS 4.9%2020-05-06

Get an alert when the next CVE fix lands in openstack/keystone, with the patched functions.

Monitor keystone CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in openstack/keystone changed by the most CVE fixes.

authenticate3 CVEs · keystone/service.py authenticate2 CVEs · keystone/contrib/ec2/core.py dict2 CVEs · keystone/service.py _validate_blob_update_keys2 CVEs · keystone/api/credentials.py handle_authenticate2 CVEs · keystone/api/_shared/EC2_S3_Resource.py build_token_values2 CVEs · keystone/contrib/revoke/model.py

All patched functions in openstack/keystone

Frequently asked questions

Common questions about CVE fixes to _assign_unique_id.

How many CVEs have patched _assign_unique_id?: 2 published CVEs changed _assign_unique_id in openstack/keystone, in 2 distinct patches totalling 86 changed lines, between 2020 and 2020.
What is the latest CVE that changed _assign_unique_id?: CVE-2020-12689 (OpenStack Keystone EC2 and/or credential endpoints are not protected from a scoped context), published 2020-05-06, changed lines 63 to 97 of keystone/api/credentials.py.
How does _assign_unique_id compare to the rest of openstack/keystone?: openstack/keystone has 29 CVEs with a located fix in total; 2 of them changed _assign_unique_id.
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

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/keystone CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing