Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.

InfluxDB before 2.7.5 can run out of memory

published 1 year ago
Summary

Versions of InfluxDB earlier than 2.7.5 may use too much memory when they process specially crafted tokens that contain many dot characters. This can cause the server to slow down or stop responding, affecting availability. Upgrade to version 2.7.5 or later, or add a check to reject inputs with an unusually large number of dots before they are processed.

What to do
  • Update azure influxdb to version 2.7.5-2.
Affected software
Ecosystem VendorProductAffected versions
Azure Linux:3 azure influxdb < 2.7.5-2
Fix: upgrade to 2.7.5-2
Original advisory text
CVE-2025-27144 affecting package influxdb for versions less than 2.7.5-2
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.
Timeline
Published24 Feb 2025
Updated23 Sep 2026
First seen23 Sep 2026
Sources
AZL-57129 · OSV
Track software like this
Free during beta