ActivemqApplication · Apache
CVE-2013-3060
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 · uneditedThe web console in Apache ActiveMQ before 5.8.0 does not require authentication, which allows remote attackers to obtain sensitive information or cause a denial of service via HTTP requests.
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 confidenceThe Apache ActiveMQ web console in versions prior to 5.8.0 lacks authentication enforcement, allowing any remote user to access the console without credentials. Attackers can exploit this to view sensitive information such as message queues, connections, and configuration details, or to send crafted HTTP requests that cause denial of service conditions.
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
ActivemqApplication
<= 5.7.0= 4.0= 4.0.1= 4.0.2= 4.1.0= 4.1.1= 5.0.0= 5.1.0= 5.2.0= 5.3.0= 5.3.1= 5.3.2CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:N/A:P
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 ActiveMQ versionLocate the ActiveMQ installation and check the version. In the installation directory, look for a VERSION.txt file or check the pom.xml for version information. Alternatively, check the 'activemq-all' JAR file name or the version reported in startup logs.Affected if The installed version is 5.7.0 or earlier, or specifically 4.0, 4.0.1, 4.0.2, 4.1.0, 4.1.1, 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.3.1, or 5.3.2.
-
Determine if web console is enabledCheck the ActiveMQ configuration files (typically conf/activemq.xml or conf/jetty.xml) for web console configuration. Look for XML elements configuring the jetty web console port (default 8161) and context paths like '/admin' or '/console'.Affected if The web console is configured and enabled in the configuration files.
-
Verify web console authentication configurationIn the jetty.xml configuration file, examine the security constraints defined for the web console. Look for security constraint definitions that specify authentication requirements (such as 'constraint' elements with 'authenticate' set to true).Affected if No authentication constraint is defined for the web console, or authentication is explicitly set to false or not configured at all.
-
Test web console access without credentialsAttempt to access the ActiveMQ web console over HTTP/HTTPS (typically port 8161) using a web browser or curl command: curl -I http://localhost:8161/admin/. Observe whether the console page loads without being prompted for credentials.Affected if The web console responds successfully without requiring any credentials, displaying the console interface or queue information.
You are affected if you are running any version of Apache ActiveMQ listed as vulnerable AND the web console is enabled and accessible without authentication credentials.
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 dataUpgrade Apache ActiveMQ to version 5.8.0 or later, which includes authentication requirements for the web console. Alternatively, if upgrading is not immediately feasible, implement network-level access controls to restrict access to the web console to authorized IP addresses only.
Fix this in Activemq
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3060 — 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-2013-3060 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