Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.2amended

OS Command Injection in git-promise

CVE-2022-24376GHSA-chj3-f7xw-367m

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm git-promise

    Affected
    <= 1.0.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.2 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2022-24376: 2.90% estimated exploitation activity in the next 30 days; percentile 86.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

All versions of package git-promise is vulnerable to Command Injection due to an inappropriate fix of a prior vulnerability in this package. Note: Please note that the vulnerability will not be fixed. The README file was updated with a warning regarding this issue. Credits @lirantal for discovering this vulnerability.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-chj3-f7xw-367m

  2. Revision 1 · created ·

    Published from osv record GHSA-chj3-f7xw-367m

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-24376

Advisory: OS Command Injection in git-promise
IDs: CVE-2022-24376, GHSA-chj3-f7xw-367m
Record: https://patchnext.com/advisories/cve-2022-24376 (revision 2, source checked 26 Oct 2026, 12:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm git-promise: affected <= 1.0.0

## Suggested inspection (read-only)
- `npm ls git-promise --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on git-promise.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-chj3-f7xw-367m (OSV record GHSA-chj3-f7xw-367m lists affected ranges: npm git-promise >=0 <=1.0.0)
- Verified: https://github.com/advisories/GHSA-chj3-f7xw-367m (GitHub-reviewed advisory GHSA-chj3-f7xw-367m lists affected ranges: npm git-promise >=0 <=1.0.0)

Commands are suggestions: review each one before running it.

Loading voting…