Sensitive-value disclosure via plaintext flow fingerprint logging
Published Feb 11, 2020 · Updated Aug 4, 2024
Information exposure in Apache NiFi 0.0.1 through 1.11.0 allows remote attackers to expose sensitive values through cluster-join errors. The flow fingerprint factory incorporates sensitive property descriptor values into the cluster and local flow fingerprints, then writes both fingerprints to application logs in plaintext when the flows cannot be inherited. The trigger requires a node to attempt to join a cluster with a non-inheritable flow; the resulting log entry exposes those values to parties able to read the logs.
Summary
What happened
Information exposure in Apache NiFi 0.0.1 through 1.11.0 allows remote attackers to expose sensitive values through cluster-join errors. The flow fingerprint factory incorporates sensitive property descriptor values into the cluster and local flow fingerprints, then writes both fingerprints to application logs in plaintext when the flows cannot be inherited. The trigger requires a node to attempt to join a cluster with a non-inheritable flow; the resulting log entry exposes those values to parties able to read the logs.
The record
- CVE
- CVE-2020-1942
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache NiFi
- Classifications
- CWE-532
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Apache NiFi 0.0.1 to 1.11.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo