Restricted-resource disclosure via integrations authorization failure
Published Feb 11, 2021 · Updated Sep 16, 2024
Improper authorization in Adobe Commerce 2.4.1 and earlier allows attackers with admin-console access to read restricted resources. Adobe identifies the integrations module as the locus but has not published the affected endpoint, failed authorization check, or input path. Successful exploitation requires access to the admin console and has no reported write or service-interruption impact.
Summary
What happened
Improper authorization in Adobe Commerce 2.4.1 and earlier allows attackers with admin-console access to read restricted resources. Adobe identifies the integrations module as the locus but has not published the affected endpoint, failed authorization check, or input path. Successful exploitation requires access to the admin console and has no reported write or service-interruption impact.
The record
- CVE
- CVE-2021-21026
- Published
- Feb 11, 2021
- Updated
- Sep 16, 2024
- Vendor
- Adobe
- Product
- Adobe Commerce
- Classifications
- CWE-285
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=unspecified <=2.3.6
- Affected versionversion=unspecified <=2.4.0-p1
- Affected versionversion=unspecified <=2.4.1
- Affected versionversion=unspecified <=None
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