Authenticated privilege escalation via supporting-file API bypass
Published Oct 22, 2024 · Updated Mar 14, 2025
API authorization bypass in Archer Platform 2024.03 through 2024.08 allows remote authenticated users to upload additional system icons. The vendor identifies the locus only as the supporting-application-file API and has not disclosed the incorrect authorization operation. Low-privileged network access is required; exploitation elevates application privileges and permits integrity changes through added icons.
Summary
What happened
API authorization bypass in Archer Platform 2024.03 through 2024.08 allows remote authenticated users to upload additional system icons. The vendor identifies the locus only as the supporting-application-file API and has not disclosed the incorrect authorization operation. Low-privileged network access is required; exploitation elevates application privileges and permits integrity changes through added icons.
The record
- CVE
- CVE-2024-49209
- Published
- Oct 22, 2024
- Updated
- Mar 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 22, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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