dbcve.org
Activemq ApolloApplication · Apache

CVE-2014-3579

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
XML external entity (XXE) vulnerability in Apache ActiveMQ Apollo 1.x before 1.7.1 allows remote consumers to have unspecified impact via vectors involving an XPath based selector when dequeuing XML messages.

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

XXE vulnerability in Apache ActiveMQ Apollo 1.x before 1.7.1 allows remote consumers to exploit XPath-based selectors when dequeuing XML messages, potentially enabling arbitrary file读取, denial of service, or server-side request forgery via malicious XML payloads.

MitigationUpgrade to Apache ActiveMQ Apollo 1.7.1 or later to obtain the patch; alternatively, disable external entity processing in the XML parser configuration and validate all incoming XML messages before processing.

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
Activemq ApolloApplication
Affected:= 1.0= 1.1= 1.2= 1.3= 1.4= 1.5= 1.6= 1.7

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
High
Availability
High

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

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

  1. Identify Apache ActiveMQ Apollo installation and version
    Locate the ActiveMQ Apollo installation directory and check the version file or banner. Common locations include /opt/activemq-apollo or the service banner when starting the broker.
    Affected if The installed version is 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, or 1.7 (versions before 1.7.1)
  2. Confirm XML message consumption with XPath selectors is in use
    Review ActiveMQ Apollo queue configurations and consumer applications to determine if XPath-based message selectors are being used to dequeue messages from XML queues.
    Affected if XPath-based selectors are actively used to select/consume XML messages from queues
  3. Check if incoming XML messages are unvalidated
    Inspect the message processing pipeline and any existing XML validation logic to determine if incoming XML messages are validated against a schema before being processed by the XPath selector.
    Affected if XML messages are processed by XPath selectors without schema validation or sanitization
  4. Inspect XML parser configuration for external entity settings
    Examine the ActiveMQ Apollo broker configuration files (typically in etc/ or conf/ directory) and the XML parser settings to determine if external entity processing is enabled.
    Affected if External entity processing is enabled in the XML parser configuration and the broker processes XML messages with XPath selectors

You are affected if you run Apache ActiveMQ Apollo versions 1.0 through 1.7 and use XPath-based selectors to consume XML messages from queues without disabling external entity processing in your XML parser.

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

Upgrade to Apache ActiveMQ Apollo 1.7.1 or later to obtain the patch; alternatively, disable external entity processing in the XML parser configuration and validate all incoming XML messages before processing.

Recommended fix High confidence

Apache ActiveMQ Apollo 1.7.1

  1. 1. Backup your current ActiveMQ Apollo configuration and data directories
  2. 2. Download Apache ActiveMQ Apollo version 1.7.1 from the official Apache archive (https://archive.apache.org/dist/activemq/activemq-apollo/)
  3. 3. Stop the currently running ActiveMQ Apollo service
  4. 4. Install version 1.7.1 following standard installation procedures
  5. 5. Restore your configuration from the backup
  6. 6. Start the upgraded ActiveMQ Apollo service
  7. 7. Verify the service is running correctly and test message dequeuing functionality

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

Fix this in Activemq Apollo Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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