← Back to results
Vulnerability record · public intelligence
CVE-2020-25675
LOW

CVE-2020-25675

Published Dec 8, 2020 · Updated Oct 23, 2026

Severity · CVSSLOW · 3.3
Known exploitationNot listed
EPSS / likelihood1.08%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

In the CropImage() and CropImageToTiles() routines of MagickCore/transform.c, rounding calculations performed on unconstrained pixel offsets was causing undefined behavior in the form of integer overflow and out-of-range values as reported by UndefinedBehaviorSanitizer. Such issues could cause a negative impact to application availability or other problems related to undefined behavior, in cases where ImageMagick processes untrusted input data. The upstream patch introduces functionality to constrain the pixel offsets and prevent these issues. This flaw affects ImageMagick versions prior to 7.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

In the CropImage() and CropImageToTiles() routines of MagickCore/transform.c, rounding calculations performed on unconstrained pixel offsets was causing undefined behavior in the form of integer overflow and out-of-range values as reported by UndefinedBehaviorSanitizer. Such issues could cause a negative impact to application availability or other problems related to undefined behavior, in cases where ImageMagick processes untrusted input data. The upstream patch introduces functionality to constrain the pixel offsets and prevent these issues. This flaw affects ImageMagick versions prior to 7.0.9-0.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. bugzilla.redhat.com ↗
  2. [debian-lts-announce] 20210323 [SECURITY] [DLA 2602-1] imagemagick security update ↗
  3. [debian-lts-announce] 20230311 [SECURITY] [DLA 3357-1] imagemagick security update ↗

Record history

Published Dec 8, 2020 · Last refreshed Oct 23, 2026