Metadata modification via ordinary-object metadata merge
Published Apr 28, 2023 · Updated Jan 30, 2025
Prototype pollution in Aedart Ion @aedart/support before 0.6.1 allows attackers to modify records via crafted base-class metadata. The resolveMetadataRecord function creates an ordinary inherited object and uses Object.assign to merge base-class Symbol.metadata into that record, permitting prototype-changing assignments. Exploitation requires a class decorated with meta() and sensitive objects stored as metadata; the consequence depends on how consuming code uses the polluted record.
Summary
What happened
Prototype pollution in Aedart Ion @aedart/support before 0.6.1 allows attackers to modify records via crafted base-class metadata. The resolveMetadataRecord function creates an ordinary inherited object and uses Object.assign to merge base-class Symbol.metadata into that record, permitting prototype-changing assignments. Exploitation requires a class decorated with meta() and sensitive objects stored as metadata; the consequence depends on how consuming code uses the polluted record.
The record
- CVE
- CVE-2023-30857
- Published
- Apr 28, 2023
- Updated
- Jan 30, 2025
- Vendor
- Aedart
- Product
- Ion
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2023CVE publishedPublication date reported by the CVE source.
- Jan 30, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.6.1
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