NifiApplication · Apache
CVE-2020-1928
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn information disclosure vulnerability was found in Apache NiFi 1.10.0. The sensitive parameter parser would log parsed values for debugging purposes. This would expose literal values entered in a sensitive property when no parameter was present.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Apache NiFi 1.10.0, the sensitive parameter parser includes debug logging that outputs parsed values. When users enter literal values directly into sensitive properties (instead of using parameter references), these literal values get written to log files, exposing sensitive information such as passwords or credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
NifiApplication
= 1.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm NiFi versionCheck the installed NiFi version by reviewing the release notes or the nifi.properties file, typically found in the NiFi/conf directory. You can also check the UI footer which displays the version.Affected if The installed version is exactly 1.10.0
-
Identify sensitive property configurationsReview all processor and controller service configurations in your NiFi flow for sensitive properties (passwords, credentials, keys). Check whether these were configured with literal values entered directly or with parameter references (${ensitiveParam}).Affected if Any sensitive properties were configured using literal values entered directly rather than parameter references in version 1.10.0
-
Examine NiFi log files for exposed valuesSearch NiFi log files (nifi-app.log, nifi-user.log in the NiFi/logs directory) for occurrences of sensitive-looking literal strings that may have been entered as property values. Look for patterns matching password, credential, or key values you recognize.Affected if Log files contain any literal sensitive values that were entered directly into sensitive properties
-
Check log level configurationVerify the logging configuration for the sensitive parameter parser. Review the log4j.xml configuration file in the NiFi/conf directory to confirm if DEBUG level logging was enabled for the relevant component.Affected if DEBUG logging was enabled for the sensitive parameter parser component in version 1.10.0
You are affected if running NiFi 1.10.0 with any sensitive properties configured using literal values entered directly, with potential exposure of those values in log files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade from NiFi 1.10.0 to a patched version. Review logs for any exposed sensitive values and rotate potentially compromised credentials.
Fix this in Nifi
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1928 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-1928 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data