dbcve.org
NifiApplication · Apache

CVE-2023-49145

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-27
Fix available
A fix is available. Upgrade to 1.24.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 0.7.0 through 1.23.2 include the JoltTransformJSON Processor, which provides an advanced configuration user interface that is vulnerable to DOM-based cross-site scripting. If an authenticated user, who is authorized to configure a JoltTransformJSON Processor, visits a crafted URL, then arbitrary JavaScript code can be executed within the session context of the authenticated user. Upgrading to Apache NiFi 1.24.0 or 2.0.0-M1 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

DOM-based cross-site scripting vulnerability in Apache NiFi's JoltTransformJSON Processor advanced configuration UI. An authenticated user with authority to configure this processor can be exploited by visiting a crafted URL, allowing arbitrary JavaScript execution within their session context. The vulnerability affects versions 0.7.0 through 1.23.2.

MitigationUpgrade Apache NiFi to version 1.24.0 or 2.0.0-M1 to remediate this vulnerability.

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, < 1.24.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. Confirm Apache NiFi version
    Check the installed NiFi version by accessing the UI (Help > About) or by examining the nifi-assembly JAR/nar file names in the installation directory, or run: ls -la nifi-* | head -20
    Affected if Version is 0.7.0 through 1.23.2 (inclusive)
  2. Verify JoltTransformJSON processor exists
    Search the NiFi flow for JoltTransformJSON processors: in the UI, use the search function to find 'JoltTransformJSON', or examine the flow.xml.gz file for occurrences of 'JoltTransformJSON'
    Affected if At least one JoltTransformJSON processor is present in the flow
  3. Confirm advanced configuration access
    In the NiFi UI, right-click on any JoltTransformJSON processor and select 'Configure', then navigate to the 'Advanced' tab, or attempt a GET request to the advanced UI endpoint for this processor type
    Affected if The advanced configuration UI is accessible for the JoltTransformJSON processor

You are affected if your NiFi version is between 0.7.0 and 1.23.2 inclusive AND you have a JoltTransformJSON processor in your flow with accessible advanced configuration UI.

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.24.0 or later
Fixed in 1.24.0
Interim mitigation

Upgrade Apache NiFi to version 1.24.0 or 2.0.0-M1 to remediate this vulnerability.

Recommended fix High confidence

1.24.0 (or 2.0.0-M1 for testing)

  1. 1. Backup your existing NiFi installation, flow.xml.gz, and configuration files
  2. 2. Stop the NiFi service
  3. 3. Download Apache NiFi 1.24.0 from the official Apache NiFi repository (nifi.apache.org)
  4. 4. Install NiFi 1.24.0 to replace the existing installation
  5. 5. Migrate any custom configuration settings from the old installation to the new version
  6. 6. Start the NiFi service
  7. 7. Log in and verify the JoltTransformJSON Processor loads correctly without XSS vulnerability
Caveat Review release notes; 2.0.0-M1 is a milestone release with potentially more breaking changes than stable 1.24.0

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

Fix this in Nifi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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