RabbitMQ 0.9.0 amqp_connection.c memcpy CONNECTION_STATE_HEADER integer overflow
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in RabbitMQ 0.9.0. This vulnerability affects the function memcpy
of the file amqp_connection.c. The manipulation of the argument CONNECTION_STATE_HEADER leads to integer overflow.
This vulnerability was named CVE-2019-18609. The attack can be initiated remotely. There is no exploit available.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability classified as critical has been found in RabbitMQ 0.9.0. This affects the function memcpy
of the file amqp_connection.c. The manipulation of the argument CONNECTION_STATE_HEADER
with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in amqp_handle_input in amqp_connection.c in rabbitmq-c 0.9.0. There is an integer overflow that leads to heap memory corruption in the handling of CONNECTION_STATE_HEADER. A rogue server could return a malicious frame header that leads to a smaller target_size value than needed. This condition is then carried on to a memcpy function that copies too much data into a heap buffer.
The weakness was shared 12/01/2019 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2019-18609 since 10/29/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.3
VulDB Base Score: 7.3
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
10/29/2019 🔍12/01/2019 🔍
12/03/2019 🔍
03/05/2024 🔍
Sources
Advisory: USN-4214-1Status: Not defined
CVE: CVE-2019-18609 (🔍)
GCVE (CVE): GCVE-0-2019-18609
GCVE (VulDB): GCVE-100-146529
Entry
Created: 12/03/2019 04:24 PMUpdated: 03/05/2024 10:13 AM
Changes: 12/03/2019 04:24 PM (38), 12/03/2019 04:29 PM (17), 03/05/2024 10:13 AM (5)
Complete: 🔍
Cache ID: 18:224:40
No comments yet. Languages: en.
Please log in to comment.