Authenticated data exposure via API-user relations
Published May 19, 2022 · Updated Aug 3, 2024
Improper sensitive-data handling in Strapi before 3.6.10 or 4.1.10 allows remote authenticated users to read API-user secrets through the admin panel. Admin API responses fail to remove private attributes from API users reached through direct or indirect content-type relationships, exposing emails and password-reset tokens. An admin-panel account and enabled password-reset endpoints are required; leaked tokens can enable account takeover and broader privilege abuse.
Summary
What happened
Improper sensitive-data handling in Strapi before 3.6.10 or 4.1.10 allows remote authenticated users to read API-user secrets through the admin panel. Admin API responses fail to remove private attributes from API users reached through direct or indirect content-type relationships, exposing emails and password-reset tokens. An admin-panel account and enabled password-reset endpoints are required; leaked tokens can enable account takeover and broader privilege abuse.
The record
- CVE
- CVE-2022-30618
- Published
- May 19, 2022
- Updated
- Aug 3, 2024
- Vendor
- Strapi
- Product
- Strapi
- Classifications
- CWE-212, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 19, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.6.10
- Affected versionversion=< 4.1.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo