NifiApplication · Apache
CVE-2017-7665
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 · uneditedIn Apache NiFi before 0.7.4 and 1.x before 1.3.0, there are certain user input components in the UI which had been guarding for some forms of XSS issues but were insufficient.
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 confidenceApache NiFi versions before 0.7.4 and 1.x before 1.3.0 contain insufficient XSS protection in certain UI user input components. While some XSS defenses were implemented, they were incomplete, allowing attackers to inject malicious scripts through these input fields.
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
<= 0.7.3= 1.0.0= 1.0.1= 1.1.0= 1.1.1= 1.1.2= 1.2.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify NiFi version from the web UIAccess the NiFi web interface and locate the version number in the footer of any page, or click the NiFi icon in the top-left corner to open the About dialog which displays the versionAffected if The displayed version is 0.7.3 or earlier, or exactly 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.1.2, or 1.2.0
-
Identify NiFi version from configuration filesLocate and read the nifi.properties file in the NiFi conf directory (typically at $NIFI_HOME/conf/nifi.properties) and look for the nifi.version propertyAffected if The nifi.version property shows a version matching the affected list in step 1
-
Verify the web UI is accessibleConfirm that the NiFi web user interface is reachable and operational (typically on port 8080 or 8443 by default)Affected if The web UI is accessible and the version from step 1 or 2 matches an affected version
-
Determine if user input components are in useIdentify if any processors, controller services, or other components that accept user-supplied input are configured and active in dataflowsAffected if Active components accept user input and the NiFi version is on the affected list - the XSS flaw exists in these input fields
You are affected if your installed Apache NiFi version is 0.7.3 or earlier, or exactly 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.1.2, or 1.2.0, and the web UI is accessible.
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 Apache NiFi to version 0.7.4 or later (for the 0.x branch) or 1.3.0 or later (for the 1.x branch) to obtain the patched input validation. Consider implementing additional output encoding and Content Security Policy headers as defense-in-depth measures.
Fix this in Nifi
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7665 — 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-2017-7665 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