dbcve.org
NifiApplication · Apache

CVE-2024-37389

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-08
Fix available
A fix is available. Upgrade to 1.27.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Apache NiFi 1.10.0 through 1.26.0 and 2.0.0-M1 through 2.0.0-M3 support a description field in the Parameter Context configuration that is vulnerable to cross-site scripting. An authenticated user, authorized to configure a Parameter Context, can enter arbitrary JavaScript code, which the client browser will execute within the session context of the authenticated user. Upgrading to Apache NiFi 1.27.0 or 2.0.0-M4 is the recommended mitigation.

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 confidence

Apache NiFi contains a stored cross-site scripting (XSS) vulnerability in the Parameter Context configuration description field. An authenticated user with Parameter Context configuration privileges can inject arbitrary JavaScript code that executes within the session context of the authenticated user viewing the configuration.

MitigationUpgrade to Apache NiFi 1.27.0 or 2.0.0-M4 to resolve the vulnerability. Users who cannot upgrade immediately should review Parameter Context configurations for malicious description field content.

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:>= 1.10.0, < 1.27.0= 2.0.0

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Determine the installed NiFi version
    Check the NiFi UI footer or the RELEASE file in the NiFi installation directory. Alternatively, query the NiFi API endpoint /nifi-api/flow/about
    Affected if The installed version is >= 1.10.0 and < 1.27.0, or equals 2.0.0 exactly
  2. Verify Parameter Contexts exist
    Navigate to the NiFi UI, go to the hamburger menu, select Controller Settings, then Parameter Contexts. Alternatively, query the NiFi API endpoint /nifi-api/flow/parameter-contexts
    Affected if No parameter contexts exist, the vulnerability cannot be exploited because there is no target for the XSS payload
  3. Inspect Parameter Context description fields for suspicious content
    In the Parameter Contexts list view, examine the Description column for each context. Look for HTML tags, script elements, javascript: URIs, or unusual encoded content that may represent an XSS payload
    Affected if Any Parameter Context has a description field containing script tags, event handlers (onclick, onerror, etc.), or other JavaScript code that was not intentionally entered by an administrator

You are affected if your NiFi version falls within the range >= 1.10.0 and < 1.27.0 or equals 2.0.0, and any Parameter Context description field contains stored JavaScript or HTML content that could execute in another user's session.

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.

dbcve · scoped
Upgrade available Upgrade to 1.27.0 or later
Fixed in 1.27.0
Interim mitigation

Upgrade to Apache NiFi 1.27.0 or 2.0.0-M4 to resolve the vulnerability. Users who cannot upgrade immediately should review Parameter Context configurations for malicious description field content.

Recommended fix High confidence

Apache NiFi 1.27.0 or 2.0.0-M4

  1. 1. Review the Apache NiFi 1.27.0 or 2.0.0-M4 release notes for any breaking changes relevant to your deployment
  2. 2. Back up your existing NiFi configuration, flow XML, and database
  3. 3. Stop the NiFi service
  4. 4. Upgrade to Apache NiFi 1.27.0 (recommended for production) or 2.0.0-M4
  5. 5. Verify the upgrade by checking that the Parameter Context description field properly escapes HTML/JavaScript content
  6. 6. Restart the NiFi service
  7. 7. Test that Parameter Context configuration works correctly
Caveat Review release notes for 1.27.0/2.0.0-M4 to assess any configuration or API changes that may affect your workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nifi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37389 — 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-2024-37389 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