GHSA-96jg-pmc4-cx39: TYPO3 CMS Insecure Deserialization
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: typo3/cms-core (Packagist) 8.7.17, 9.3.1.
Low priority for now. Upgrade to typo3/cms-core (Packagist) 8.7.17, 9.3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
It has been discovered that the Form Framework (system extension `form`) is vulnerable to Insecure Deserialization when being used with the additional PHP PECL package `yaml`, which is capable of unserializing YAML contents to PHP objects. A valid backend user account as well as having PHP setting `yaml.decode_php` enabled is needed to exploit this vulnerability (which is the default value according to PHP documentation).
- Published
- May 30, 2024
- Updated
- Dec 5, 2024
- EPSS
- —
- CWE
- CWE-502
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Packagist | typo3/cms-core | pkg:composer/typo3/cms-core |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | typo3/cms-core | from 8.5.0 · before 8.7.17 | 8.7.17 |
| Packagist | typo3/cms-core | from 9.0.0 · before 9.3.1 | 9.3.1 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-cc97-g92w-jm65TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution39Monitor
- GHSA-x428-565f-8xj2TYPO3 Arbitrary Code Execution and Cross-Site Scripting in Backend API35Monitor
- GHSA-f9hr-7cfq-mjg2TYPO3 Arbitrary Code Execution via File List Module35Monitor
Published before and after this one in the same product
- ← EarlierGHSA-45wj-jv2h-jwrfMay 30, 2024 · TYPO3 CMS Privilege Escalation and SQL Injection30Monitor
- ← EarlierGHSA-wg8h-gxf4-g4ghMay 30, 2024 · TYPO3 Cross-Site Scripting in Online Media Asset Rendering24Monitor
- Later →GHSA-g4c9-qfvw-fmr4May 30, 2024 · TYPO3 Cross-Site Scripting in Backend Modal Component24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:typo3/cms-core | 8.7.17 | Package registry (OSV) |
| Packagist:typo3/cms-core | 9.3.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- GHSA-5h5v-m596-r6rf0 days apartTYPO3 Possible Insecure Deserialization in Extbase Request Handling32Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- GHSA-rxc9-f2x6-qh4w0 days apartTYPO3 Security Misconfiguration for Backend User Accounts30Monitor
- GHSA-x4rj-f7m6-42c30 days apartTYPO3 CMS Authentication Bypass vulnerability30Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
osv
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)
job = pickle.loads(payload)Fixed
payload = sock.recv(65536)
if not hmac.compare_digest(sign(payload), header_sig):
raise PermissionError("invalid signature")
job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.