Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

CVE-2015-5254

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up

Improper Input Validation in Apache ActiveMQ

Critical severity GitHub Reviewed PublishedMay 13, 2022 to the GitHub Advisory Database • UpdatedDec 20, 2023

Package

mavenorg.apache.activemq:activemq-client (Maven)

Affected versions

>= 5.0.0, < 5.11.3
>= 5.12.0, < 5.12.2

Patched versions

5.11.3
5.12.2

Description

Apache ActiveMQ 5.x before 5.13.0 does not restrict the classes that can be serialized in the broker, which allows remote attackers to execute arbitrary code via a crafted serialized Java Message Service (JMS) ObjectMessage object.

References

Published by theNational Vulnerability DatabaseJan 8, 2016
Published to the GitHub Advisory DatabaseMay 13, 2022
ReviewedJul 6, 2022
Last updatedDec 20, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector:More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity:More severe for the least complex attacks.
Privileges required:More severe if no privileges are required.
User interaction:More severe when no user interaction is required.
Scope:More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality:More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity:More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability:More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided byFIRST.
(99th percentile)

Weaknesses

CVE ID

CVE-2015-5254

GHSA ID

GHSA-q9hr-3pg4-3jp4

Source code

Credits

LoadingChecking history
See something to contribute?Suggest improvements for this vulnerability.
[8]ページ先頭
©2009-2025 Movatter.jp