dbcve.org
NifiApplication · Apache

CVE-2017-5635

HIGH · 7.5 CVSS v3.0 Published 2017-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, if an anonymous user request is replicated to another node, the originating node identity is used rather than the "anonymous" user.

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 · moderate confidence

In Apache NiFi clustered deployments, when an anonymous user request is replicated across nodes, the originating node's identity is incorrectly used instead of preserving the 'anonymous' user identity. This allows privilege escalation where anonymous users may inherit higher-privileged node identities.

MitigationUpgrade Apache NiFi to version 0.7.2 or 1.1.2 or later. In the interim, strictly control cluster node-to-node communication and implement access logging to detect anomalous identity usage.

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
Affected:= 0.7.0= 0.7.1= 1.1.0= 1.1.1

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NiFi version
    Run 'nifi.sh --version' or check the release notes or log files for the installed NiFi version. Compare against affected versions: 0.7.0, 0.7.1, 1.1.0, or 1.1.1
    Affected if The installed version is one of the four affected versions listed in the CVE
  2. Determine if NiFi is clustered
    Check the nifi.properties configuration file for the property 'nifi.cluster.is.enabled'. A value of 'true' indicates cluster mode is active
    Affected if Clustering is enabled (nifi.cluster.is.enabled=true) - this vulnerability only affects clustered deployments
  3. Verify anonymous access configuration
    Check nifi.properties for properties related to anonymous access, such as 'nifi.security.anonymous.authorizer.enabled' or review the authorizer configuration to see if anonymous users are permitted
    Affected if Anonymous access is enabled in the authorization configuration
  4. Inspect identity propagation in cluster communication
    Review cluster node-to-node communication logs and access logs for instances where requests appear to originate from node identities rather than 'anonymous' when initiated by anonymous users
    Affected if Logs show anonymous requests being attributed to node identities instead of the anonymous user principal

You are affected if NiFi is version 0.7.0, 0.7.1, 1.1.0, or 1.1.1 AND is running in cluster mode with anonymous access enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache NiFi to version 0.7.2 or 1.1.2 or later. In the interim, strictly control cluster node-to-node communication and implement access logging to detect anomalous identity usage.

Fix this in Nifi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5635 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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