Skip to main content
Public proof of conceptFix available

CVE-2022-24720

A public proof of concept exists; no exploitation attested.

  • Published2022-03-01
  • WeaknessCWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

image_processing is an image processing wrapper for libvips and ImageMagick/GraphicsMagick. Prior to version 1.12.2, using the `#apply` method from image_processing to apply a series of operations that are coming from unsanitized user input allows the attacker to execute shell commands. This method is called internally by Active Storage variants, so Active Storage is vulnerable as well. The vulnerability has been fixed in version 1.12.2 of image_processing. As a workaround, users who process based on user input should always sanitize the user input by allowing only a constrained set of operations.

Timeline

dates in UTC
  1. 2022-03-0123:15CVE publishedNVD

Versions per branch

NVD · OSV
Debian debian linux
BranchAffectedFixed in
11.0= 11.0no fix published
Image processing project image processing
BranchAffectedFixed in
1.12< 1.12.21.12.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • janko image_processing
    Affected
    • = < 1.12.2no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-12-31

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • ruby-image-processingUbuntu:22.04:LTSall versions · fixed in 1.10.3-1ubuntu0.22.04.1
  • ruby-image-processingUbuntu:20.04:LTSall versions · fixed in 1.10.3-1ubuntu0.20.04.1
  • ruby-image-processingDebian:12all versions · fixed in 1.10.3-2
  • ruby-image-processingDebian:11all versions · fixed in 1.10.3-1+deb11u1

Vendor advisories

  • CVE-2022-24720 Red Hat Product Security

    rubygem-image_processing: remote shell execution via #apply method

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2025-04-22
  • CNACVSS 3.19.8known since 2026-10-23
  • NVDCVSS 3.19.8read 2026-10-23
  • NVDCVSS 2.010read 2026-10-23
  • CNAweakness (CWE)CWE-20known since 2026-10-23
  • FIRST EPSSEPSS score2.7 %2026-11-09
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryCRITICAL2022-03-01

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2022-03-01
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-cxf7-qrc5-9446

Frequently asked questions

What is CVE-2022-24720?

image_processing is an image processing wrapper for libvips and ImageMagick/GraphicsMagick. Prior to version 1.12.2, using the `#apply` method from image_processing to apply a series of operations that are coming from unsanitized user input allows the attacker to execute shell commands. This method is called internally by Active Storage variants, so Active Storage is vulnerable as well. The vulnerability has been fixed in version 1.12.2 of image_processing. As a workaround, users who process based on user input should always sanitize the user input by allowing only a constrained set of operations.

Is CVE-2022-24720 actively exploited?

A proof-of-concept exploit exists for CVE-2022-24720, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2022-24720?

CVE-2022-24720 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running image_processing? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record