Skip to content
Noroxi
CVE-2022-22984· NVD / CVE Program· CNA snyk

The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.31.3; the package snyk-gradle-plugin before 3.24.5; the package @snyk

Noroxi assessment

Priority: Monitor (action score 26/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: 3.1% (FIRST EPSS); higher than 87.7% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: @snyk/snyk-cocoapods-plugin (npm) 2.5.3; @snyk/snyk-hex-plugin (npm) 1.1.6; snyk (npm) 1.1064.0.

Low priority for now. Upgrade to @snyk/snyk-cocoapods-plugin (npm) 2.5.3; @snyk/snyk-hex-plugin (npm) 1.1.6; snyk (npm) 1.1064.0 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

The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.31.3; the package snyk-gradle-plugin before 3.24.5; the package @snyk/snyk-cocoapods-plugin before 2.5.3; the package snyk-sbt-plugin before 2.16.2; the package snyk-python-plugin before 1.24.2; the package snyk-docker-plugin before 5.6.5; the package @snyk/snyk-hex-plugin before 1.1.6 are vulnerable to Command Injection due to an incomplete fix for [CVE-2022-40764](https://security.snyk.io/vuln/SNYK-JS-SNYK-3037342). A successful exploit allows attackers to run arbitrary commands on the host system where the Snyk CLI is installed by passing in crafted command line flags. In order to exploit this vulnerability, a user would have to execute the snyk test command on untrusted files. In most cases, an attacker positioned to control the command line arguments to the Snyk CLI would already be positioned to execute arbitrary commands. However, this could be abused in specific scenarios, such as continuous integration pipelines, where developers can control the arguments passed to the Snyk CLI to leverage this component as part of a wider attack against an integration/build pipeline. This issue has been addressed in the latest Snyk Docker images available at https://hub.docker.com/r/snyk/snyk as of 2022-11-29. Images downloaded and built prior to that date should be updated. The issue has also been addressed in the Snyk TeamCity CI/CD plugin as of version v20221130.093605.

MediumCVSS 6.3 · v3.1—No exploit Fix available
Published
Nov 30, 2022
Updated
Jun 17, 2026
EPSS
3.1% · 87th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
25 / 40 · 6.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.1%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.3
CNA · snyk
5.0
1.3 point gap

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

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-22984

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.

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
snyksnyk cli
snyksnyk cocoapods cli
snyksnyk docker cli
snyksnyk gradle cli
snyksnyk hex cli
snyksnyk maven cli
snyksnyk python cli
snyksnyk sbt cli

Affected versions

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

  • snyk snyk clibefore 1.1064.0
  • snyk snyk cocoapods clibefore 2.5.3
  • snyk snyk docker clibefore 5.6.5
  • snyk snyk gradle clibefore 3.24.5
  • snyk snyk hex clibefore 1.1.6
  • snyk snyk maven clibefore 2.31.3
  • snyk snyk python clibefore 1.24.2
  • snyk snyk sbt clibefore 2.16.2

Versions reported by the vendor

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

  • n/a @snyk/snyk-cocoapods-plugin

    • unspecified and later · before 2.5.3affected
  • n/a @snyk/snyk-hex-plugin

    • unspecified and later · before 1.1.6affected
  • n/a snyk

    • unspecified and later · before 1.1064.0affected
  • n/a snyk-docker-plugin

    • unspecified and later · before 5.6.5affected
  • n/a snyk-gradle-plugin

    • unspecified and later · before 3.24.5affected
  • n/a snyk-mvn-plugin

    • unspecified and later · before 2.31.3affected
  • n/a snyk-python-plugin

    • unspecified and later · before 1.24.2affected
  • n/a snyk-sbt-plugin

    • unspecified and later · before 2.16.2affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
npm@snyk/snyk-cocoapods-pluginbefore 2.5.32.5.3
npm@snyk/snyk-hex-pluginbefore 1.1.61.1.6
npmsnykbefore 1.1064.01.1064.0
npmsnyk-docker-pluginbefore 5.6.55.6.5
npmsnyk-gradle-pluginbefore 3.24.53.24.5
npmsnyk-mvn-pluginbefore 2.31.32.31.3
npmsnyk-python-pluginbefore 1.24.21.24.2
npmsnyk-sbt-pluginbefore 2.16.22.16.2

Same product

snyk: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-24441The package snyk before 1.1064.0 are vulnerable to Code Injection when analyzing a project.
    35Monitor
  • CVE-2024-48964The package Snyk CLI before 1.1294.0 is vulnerable to Code Injection when scanning an untrusted Gradle project.
    30Monitor
  • CVE-2024-48963The package Snyk CLI before 1.1294.0 is vulnerable to Code Injection when scanning an untrusted PHP project.
    30Monitor

Published before and after this one in the same product

  • Later →CVE-2025-6624Jun 26, 2025 · Versions of the package snyk before 1.1297.3 are vulnerable to Insertion of Sensitive Information into Log File through local Snyk CLI debug
    4Monitor

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
npm:@snyk/snyk-cocoapods-plugin2.5.3Package registry (OSV)
npm:@snyk/snyk-hex-plugin1.1.6Package registry (OSV)
npm:snyk1.1064.0Package registry (OSV)
npm:snyk-docker-plugin5.6.5Package registry (OSV)
npm:snyk-gradle-plugin3.24.5Package registry (OSV)
npm:snyk-mvn-plugin2.31.3Package registry (OSV)
npm:snyk-python-plugin1.24.2Package registry (OSV)
npm:snyk-sbt-plugin2.16.2Package 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).

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

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

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

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

CVSS vector

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

nvd-primary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const host = req.body.host;exec("ping -c 1 " + host, onResult);

Fixed

ts
const host = req.body.host;if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);execFile("ping", ["-c", "1", host], onResult);

Change log

  1. Fix✗ → ✓

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

References

All records