How severe is CVE-2022-0203?

CVE-2022-0203 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-0203?

CVE-2022-0203 affects the following packages: bytefury/crater (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-0203?

Update bytefury/crater to 6.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0203 is resolved across your whole dependency graph.

How do I detect CVE-2022-0203 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bytefury/crater, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-0203 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-0203 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-0203, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-0203?

CVE-2022-0203 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-0203?

CVE-2022-0203 is classified as CWE-284 (CWE-284), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-0203 published, and has it been updated?

CVE-2022-0203 was published on January 26, 2022 and was last updated on August 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2022-0203 — crater

HIGHFix: crater-invoice/crater@dd324c8

CVE-2022-0203 is a high-severity (CVSS 7.5) CWE-284 vulnerability in bytefury/crater. 1 public exploit reference exists, so weaponization risk is real. A fix is available for bytefury/crater — see the affected versions and patch details below.

Improper Access Control in crater-invoice/crater

Also known asGHSA-xh9g-cp3v-p8q4

Published

Jan 26, 2022

Updated

Aug 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-0203 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐘bytefury/crater

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Improper Access Control in GitHub repository crater-invoice/crater prior to 6.0.2.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`bytefury/crater`	all versions	6.0.2`composer require bytefury/crater:^6.0.2`

Affected Products

1 product · 1 configurations

Application

cratercraterapp

< 6.0.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Improper Access Control in GitHub repository crater-invoice/crater prior…

huntr.devNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bytefury/crater, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bytefury/crater to 6.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0203 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Crater Invoice prior to version 6.0.2 has a missing authorization vulnerability..

O3 Security · Impact-Aware SCA

Is CVE-2022-0203 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-284CWE-284 CWE-862CWE-862

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Jan 26, 2022

First exploit

Feb 2, 2022

7 days after disclosure — rapid exploitation

Last updated

Aug 27, 2026

Identifiers

CVE-2022-0203

GHSA-xh9g-cp3v-p8q4

References

Advisorygithub.com Advisorynvd.nist.gov Fixgithub.com Webhuntr.dev Packagegithub.com

Related vulnerabilities

Also affects bytefury/crater

This CVE is high severity; 2 of 3 other CVEs affecting bytefury/crater are rated as high or higher (top: high).

CVE-2022-0372CVE-2022-0242CVE-2021-4080

Same weakness: CWE-284

This CVE is high severity; 2 of 5 other CVEs with CWE-284 are rated as high or higher (top: high).

CVE-2026-58197CVE-2026-61700CVE-2026-46696CVE-2026-65915CVE-2026-55621Browse all CWE-284

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 27, 2026

CVE-2022-0203 — crater

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-0203 in your dependencies?