NifiApplication · Apache
CVE-2018-1310
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 · uneditedApache NiFi JMS Deserialization issue because of ActiveMQ client vulnerability. Malicious JMS content could cause denial of service. See ActiveMQ CVE-2015-5254 announcement for more information. The fix to upgrade the activemq-client library to 5.15.3 was applied on the Apache NiFi 1.6.0 release. Users running a prior 1.x release should upgrade to the appropriate release.
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 contains a JMS deserialization vulnerability stemming from the bundled ActiveMQ client library (CVE-2015-5254). Maliciously crafted JMS content can trigger the vulnerable deserialization path, leading to denial of service. The fix requires upgrading the activemq-client library to version 5.15.3, which was incorporated into Apache NiFi 1.6.0.
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.6.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 installed Apache NiFi versionCheck the NiFi version by inspecting the nifi.properties file, the NiFi UI welcome page, or running 'bin/nifi.sh version' from the NiFi installation directory. Look for a version number like 1.5.x, 1.4.x, 1.3.x, etc.Affected if The installed version is any release prior to 1.6.0 (e.g., 1.5.0, 1.4.0, 1.3.0) or if the version cannot be determined and the product is known to be Apache NiFi prior to 1.6.0
-
Verify presence of JMS processorsLog into the NiFi web UI and search for processors of type 'ConsumeJMS', 'PublishJMS', or similar JMS-related processors. Alternatively, inspect the flow.xml.gz file for any JMS processor component definitions.Affected if Any JMS processor (ConsumeJMS, PublishJMS, etc.) is actively configured or enabled in the NiFi flow
-
Locate bundled activemq-client libraryNavigate to the NiFi installation directory and locate the activemq-client jar file, typically found in the lib folder. The file is typically named activemq-client-<version>.jar.Affected if The activemq-client library version is older than 5.15.3, or if the library file exists but its version cannot be determined and NiFi is below 1.6.0
A user is affected if their Apache NiFi installation is version 1.6.0 or lower, AND JMS processors are in use or the vulnerable activemq-client library (below 5.15.3) is present in the installation.
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 data1.6.0
Upgrade Apache NiFi to version 1.6.0 or later. For earlier 1.x versions, upgrade the activemq-client library to 5.15.3 and verify JMS processors function correctly.
Fix this in Nifi
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1310 — 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-2018-1310 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