CVE-2020-9487 json
Missing Authentication for Critical Function in Apache NiFi
published 6y ago modified 2mo ago also BIT-nifi-2020-9487 , EUVD-2022-0434 , GHSA-3pp3-77j6-8ph6
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
In Apache NiFi 1.0.0 to 1.11.4, the NiFi download token (one-time password) mechanism used a fixed cache size and did not authenticate a request to create a download token, only when attempting to use the token to access the content. An unauthenticated user could repeatedly request download tokens, preventing legitimate users from requesting download tokens.
Patch / fix
Is CVE-2020-9487 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.05% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.nifi:nifi | >=1.0.0, <1.12.0-RC1 |
1.12.0-RC1 |
| bitnami | nifi | >=1.0.0, <=1.11.4 |
no fix listed |
Affected products
- n/a Apache NiFi
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
github.com
/apache/nifi/commit/01e42dfb3291c3a3549023edadafd2d8023f3042
web
-
nifi.apache.org
/security#CVE-2020-9487
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-9487
advisory, web
Sources
- CVE List CVE-2020-9487
- GitHub Advisory GHSA-3pp3-77j6-8ph6
- NVD CVE-2020-9487
- OSV BIT-nifi-2020-9487
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.