CVE-2022-2626
CVE-2022-2626 — Incorrect Privilege Assignment in hestiacp/hestiacp
Incorrect Privilege Assignment in GitHub repository hestiacp/hestiacp prior to 1.6.6.
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
9.1
CRITICAL
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 |
|---|---|---|---|---|---|
| 9.1 | CVSS 3.0 | CRITICAL | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-266
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 /hestiacp.
References
2 on the record
- huntr.dev/bounties/704aacc9-edff-4da5-90a6-4adf8dbf36fe
x_refsource_CONFIRM
- github.com/hestiacp/hestiacp/commit/b178b9719bb2c98cf8a6db70065086f596afad81
x_refsource_MISC
Elsewhere on this site
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.