CVE-2020-9482
mediumpriority · track · 27EPSS 0.027 · 86 %ileEUUSEPSS · scored 2026-10-27
If NiFi Registry 0.1.0 to 0.5.0 uses an authentication mechanism other than PKI, when the user clicks Log Out, NiFi Registry invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to make API requests to NiFi Registry.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
- Maven org.apache.nifi.registry:nifi-registry-web-api0.1.0 → 0.7.0osvUSpkg:maven/org.apache.nifi.registry/nifi-registry-web-api
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-rcwj-2hj2-vmjjInsufficient Session Expiration in Apache NiFi Registry2022-02-09ghsa · osvUS
If NiFi Registry 0.1.0 to 0.5.0 uses an authentication mechanism other than PKI, when the user clicks Log Out, NiFi Registry invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to make API requests to NiFi Registry.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (4)
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan