Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2022-24828: Missing input validation can lead to command execution in composer

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: composer (Debian:12) 2.2.12-1; php-composer (openSUSE:Leap 15.3) 1.10.26-bp153.2.6.1; php-composer2 (openSUSE:Leap 15.4) 2.2.3-150400.3.3.1.

Low priority for now. Upgrade to composer (Debian:12) 2.2.12-1; php-composer (openSUSE:Leap 15.3) 1.10.26-bp153.2.6.1; php-composer2 (openSUSE:Leap 15.4) 2.2.3-150400.3.3.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Composer is a dependency manager for the PHP programming language. Integrators using Composer code to call `VcsDriver::getFileContent` can have a code injection vulnerability if the user can control the `$file` or `$identifier` argument. This leads to a vulnerability on packagist.org for example where the composer.json's `readme` field can be used as a vector for injecting parameters into hg/Mercurial via the `$file` argument, or git via the `$identifier` argument if you allow arbitrary data there (Packagist does not, but maybe other integrators do). Composer itself should not be affected by the vulnerability as it does not call `getFileContent` with arbitrary data into `$file`/`$identifier`. To the best of our knowledge this was not abused, and the vulnerability has been patched on packagist.org and Private Packagist within a day of the vulnerability report.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Apr 13, 2022
Updated
Jun 17, 2026
EPSS
1.8% · 79th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · GitHub_M
8.3
0.5 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-24828

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for getcomposer records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
getcomposercomposer
tenabletenable.sc
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora34
  • fedoraproject fedora35
  • fedoraproject fedora36
  • getcomposer composer2.0.0 and later · before 2.2.12
  • getcomposer composer2.3.0 and later · before 2.3.5
  • getcomposer composerbefore 1.10.26
  • tenable tenable.scbefore 5.21.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • composer composer

    • < 1.10.26, >= 2.0.0, < 2.2.12, >= 2.3, < 2.3.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12composerbefore 2.2.12-12.2.12-1
openSUSE:Leap 15.3php-composerbefore 1.10.26-bp153.2.6.11.10.26-bp153.2.6.1
openSUSE:Leap 15.4php-composer2before 2.2.3-150400.3.3.12.2.3-150400.3.3.1
openSUSE:Tumbleweedphp-composerbefore 1.10.26-1.11.10.26-1.1
openSUSE:Tumbleweedphp-composer2before 2.3.5-1.12.3.5-1.1
Packagistcomposer/composerfrom 2.0 · before 2.2.122.2.12
Packagistcomposer/composerfrom 2.3 · before 2.3.52.3.5
Packagistcomposer/composerbefore 1.10.261.10.26
SUSE:Linux Enterprise Module for Web and Scripting 15 SP4php-composer2before 2.2.3-150400.3.3.12.2.3-150400.3.3.1
SUSE:Package Hub 15 SP3php-composerbefore 1.10.26-bp153.2.6.11.10.26-bp153.2.6.1

Same product

getcomposer: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-41116Command injection in composer on Windows
    40Plan
  • CVE-2026-40261Composer has Command Injection via Malicious Perforce Reference
    36Monitor
  • CVE-2021-29472Missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on systems with Mercurial in composer
    36Monitor

Published before and after this one in the same product

  • Later →CVE-2015-8371Sep 21, 2023 · Composer before 2016-02-10 allows cache poisoning from other projects built on the same host.
    35Monitor
  • Later →CVE-2023-43655Sep 29, 2023 · Remote Code Execution via web-accessible composer.phar
    35Monitor
  • Later →CVE-2024-24821Feb 8, 2024 · Code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php in Composer
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:composer2.2.12-1 · Debian:12Package registry (OSV)
opensuse:php-composer1.10.26-bp153.2.6.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:php-composer22.2.3-150400.3.3.1 · openSUSE:Leap 15.4Package registry (OSV)
Packagist:composer/composer1.10.26Package registry (OSV)
Packagist:composer/composer2.2.12Package registry (OSV)
Packagist:composer/composer2.3.5Package registry (OSV)
suse:php-composer1.10.26-bp153.2.6.1 · SUSE:Package Hub 15 SP3Package registry (OSV)
suse:php-composer22.2.3-150400.3.3.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records