CVE-2022-0203
CVE-2022-0203 — Improper Access Control in crater-invoice/crater
Improper Access Control in GitHub repository crater-invoice/crater prior to 6.0.2.
Published Updated Sources: cvelistV5, @huntrdev
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
1%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-284
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1027.009Obfuscated Files or Information: Embedded Payloads
- T1546.004Event Triggered Execution: .bash_profile and .bashrc
- T1546.016Event Triggered Execution: Installer Packages
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /crater.
References
2 on the record
- huntr.dev/bounties/395fc553-2b90-4e69-ba07-a316e1c06406
x_refsource_CONFIRM
- github.com/crater-invoice/crater/commit/dd324c8bb6b17009f82afe8bc830caec7241e992
x_refsource_MISC
Elsewhere on this site
- crater invoiceevery CVE for this vendor
- CWE-284other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.