paho.mqtt.golang: paho.mqtt.golang: Integer Overflow in UTF-8 String Encoding
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Eclipse Foundation | paho.mqtt.golang (Go MQTT v3.1 library) | unaffected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Eclipse | Paho Go Mqtt | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-32fw-gq77-f2f2 | Eclipse Paho Go MQTT may incorrectly encode strings if length exceeds 65535 bytes |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.243% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eclipse paho Mqtt
|
|
| CPEs | cpe:2.3:a:eclipse:paho_mqtt:*:*:*:*:*:go:*:* | |
| Vendors & Products |
Eclipse paho Mqtt
|
|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | paho.mqtt.golang: paho.mqtt.golang: Integer Overflow in UTF-8 String Encoding | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eclipse
Eclipse paho Go Mqtt |
|
| Vendors & Products |
Eclipse
Eclipse paho Go Mqtt |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Eclipse Paho Go MQTT v3.1 library (paho.mqtt.golang) versions <=1.5.0 UTF-8 encoded strings, passed into the library, may be incorrectly encoded if their length exceeds 65535 bytes. This may lead to unexpected content in packets sent to the server (for example, part of an MQTT topic may leak into the message body in a PUBLISH packet). The issue arises because the length of the data passed in was converted from an int64/int32 (depending upon CPU) to an int16 without checks for overflows. The int16 length was then written, followed by the data (e.g. topic). This meant that when the data (e.g. topic) was over 65535 bytes then the amount of data written exceeds what the length field indicates. This could lead to a corrupt packet, or mean that the excess data leaks into another field (e.g. topic leaks into message body). | |
| Weaknesses | CWE-197 CWE-681 |
|
| References |
| |
| Metrics |
cvssV4_0
|