CVE-2020-9486 json
Insertion of Sensitive Information into Log File in Apache NiFi Stateless
published 6y ago modified 2mo ago also BIT-nifi-2020-9486 , EUVD-2022-0596 , GHSA-g644-pr5v-vppf
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
In Apache NiFi 1.10.0 to 1.11.4, the NiFi stateless execution engine produced log output which included sensitive property values. When a flow was triggered, the flow definition configuration JSON was printed, potentially containing sensitive values in plaintext.
Patch / fix
Is CVE-2020-9486 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.56% chance of exploitation in the next 30 days, higher than 89% 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:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.nifi:nifi-stateless | >=1.10.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-532 Insertion of Sensitive Information into Log File
References
-
github.com
/apache/nifi/commit/148537d64a017b73160b0d49943183c18f883ab0
web
-
nifi.apache.org
/security#CVE-2020-9486
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-9486
advisory, web
-
github.com
/apache/nifi
package
Sources
- CVE List CVE-2020-9486
- GitHub Advisory GHSA-g644-pr5v-vppf
- NVD CVE-2020-9486
- OSV BIT-nifi-2020-9486
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.