Sandbox escape via unchecked ArrayAccess attributes
Published Nov 6, 2024 · Updated Nov 7, 2024
Sandbox escape in Twig before 3.11.2 and 3.12.0 through 3.14.0 allows remote authenticated users to read restricted object attributes. CoreExtension::getAttribute resolves ArrayAccess offsets and invokes __isset() before the sandbox policy calls checkPropertyAllowed on the requested attribute. Exploitation requires sandbox mode, a user-controlled template expression, and an application-provided ArrayAccess object; the demonstrated consequence is restricted-data disclosure.
Summary
What happened
Sandbox escape in Twig before 3.11.2 and 3.12.0 through 3.14.0 allows remote authenticated users to read restricted object attributes. CoreExtension::getAttribute resolves ArrayAccess offsets and invokes __isset() before the sandbox policy calls checkPropertyAllowed on the requested attribute. Exploitation requires sandbox mode, a user-controlled template expression, and an application-provided ArrayAccess object; the demonstrated consequence is restricted-data disclosure.
The record
- CVE
- CVE-2024-51755
- Published
- Nov 6, 2024
- Updated
- Nov 7, 2024
- Vendor
- Twig
- Product
- Twig
- Classifications
- CWE-668
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 6, 2024CVE publishedPublication date reported by the CVE source.
- Nov 7, 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.11.2
- Affected versionversion=>= 3.12.0, < 3.14.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