Vulnerabilities
Misconfiguration
Compliance
Cryptography
CVE Vulnerabilities

CVE-2023-34151

Integer Overflow or Wraparound

Published: May 30, 2023 | Modified: Jun 17, 2026
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
5.5 MODERATE
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2023-34151
CWEhttps://cwe.mitre.org/data/definitions/190.html

A vulnerability was found in ImageMagick. This security flaw ouccers as an undefined behaviors of casting double to size_t in svg, mvg and other coders (recurring bugs of CVE-2022-32546).

Weakness

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 occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Affected Software

NameVendorStart VersionEnd Version
ImagemagickImagemagick*7.1.1-11 (excluding)
ImagemagickUbuntubionic*
ImagemagickUbuntudevel*
ImagemagickUbuntuesm-apps/focal*
ImagemagickUbuntuesm-apps/jammy*
ImagemagickUbuntuesm-apps/noble*
ImagemagickUbuntuesm-apps/resolute*
ImagemagickUbuntuesm-infra-legacy/trusty*
ImagemagickUbuntuesm-infra-legacy/xenial*
ImagemagickUbuntuesm-infra/bionic*
ImagemagickUbuntuesm-infra/xenial*
ImagemagickUbuntufocal*
ImagemagickUbuntujammy*
ImagemagickUbuntukinetic*
ImagemagickUbuntulunar*
ImagemagickUbuntumantic*
ImagemagickUbuntunoble*
ImagemagickUbuntuoracular*
ImagemagickUbuntuplucky*
ImagemagickUbuntuquesting*
ImagemagickUbunturesolute*
ImagemagickUbuntustonking*
ImagemagickUbuntutrusty*
ImagemagickUbuntutrusty/esm*
ImagemagickUbuntuupstream*
ImagemagickUbuntuxenial*

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
  • Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
  • Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
  • Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
  • Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
  • Understand the programming language’s underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, “not-a-number” calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
  • Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use