GHSA-ppgf-8745-8pgx: Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Fixed version: typo3/cms (Packagist) 7.6.30, 8.7.17, 9.3.2.
Low priority for now. Upgrade to typo3/cms (Packagist) 7.6.30, 8.7.17, 9.3.2 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
Phar files (formerly known as "PHP archives") can act als self extracting archives which leads to the fact that source code is executed when Phar files are invoked. The Phar file format is not limited to be stored with a dedicated file extension - "bundle.phar" would be valid as well as "bundle.txt" would be. This way, Phar files can be obfuscated as image or text file which would not be denied from being uploaded and persisted to a TYPO3 installation. Due to a missing sanitization of user input, those Phar files can be invoked by manipulated URLs in TYPO3 backend forms. A valid backend user account is needed to exploit this vulnerability. In theory the attack vector would be possible in the TYPO3 frontend as well, however no functional exploit has been identified so far.
- Published
- Jun 5, 2024
- Updated
- Dec 2, 2024
- EPSS
- —
- CWE
- CWE-502
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- 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 | pkg:composer/typo3/cms |
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 | from 7.0.0 · before 7.6.30 | 7.6.30 |
| Packagist | typo3/cms | from 8.0.0 · before 8.7.17 | 8.7.17 |
| Packagist | typo3/cms | from 9.0.0 · before 9.3.2 | 9.3.2 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-67wg-6j7r-mqh8Arbitrary Code Execution in TYPO3 CMS39Monitor
- GHSA-gwfx-p7mr-f92vMissing Access Check in TYPO3 CMS36Monitor
- GHSA-8h4m-r4wm-xj7rTYPO3 Arbitrary Code Execution via File List Module35Monitor
Published before and after this one in the same product
- ← EarlierGHSA-7qwg-fcpw-xg5gJun 5, 2024 · Privilege Escalation & SQL Injection in TYPO3 CMS35Monitor
- ← EarlierGHSA-c7p6-3c9c-f88qJun 5, 2024 · Information Disclosure in TYPO3 CMS14Monitor
- Later →GHSA-g46h-v2cc-6c94Jun 5, 2024 · Information Disclosure in TYPO3 CMS17Monitor
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 | 7.6.30 | Package registry (OSV) |
| Packagist:typo3/cms | 8.7.17 | Package registry (OSV) |
| Packagist:typo3/cms | 9.3.2 | 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-8h28-f46f-m87h0 days apartInsecure Deserialization in TYPO3 CMS0Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataRoot 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 (2)
- Fix✗ → ✓
- CVSS8 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.