GHSA-cc97-g92w-jm65: TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution
Noroxi assessment
Priority: Monitor (action score 39/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. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: typo3/cms-core (Packagist) 7.6.30, 8.7.17, 9.3.2.
Low priority for now. Upgrade to typo3/cms-core (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
- May 30, 2024
- Updated
- Dec 5, 2024
- EPSS
- —
- CWE
- CWE-74
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 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 7.0.0 · before 7.6.30 | 7.6.30 |
| Packagist | typo3/cms-core | from 8.0.0 · before 8.7.17 | 8.7.17 |
| Packagist | typo3/cms-core | 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-x428-565f-8xj2TYPO3 Arbitrary Code Execution and Cross-Site Scripting in Backend API35Monitor
- GHSA-f9hr-7cfq-mjg2TYPO3 Arbitrary Code Execution via File List Module35Monitor
- GHSA-5h5v-m596-r6rfTYPO3 Possible Insecure Deserialization in Extbase Request Handling32Monitor
Published before and after this one in the same product
- ← EarlierGHSA-gqqf-g5r7-84vfSep 15, 2022 · TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection24Monitor
- ← EarlierGHSA-x4rj-f7m6-42c3May 30, 2024 · TYPO3 CMS Authentication Bypass vulnerability30Monitor
- Later →GHSA-45wj-jv2h-jwrfMay 30, 2024 · TYPO3 CMS Privilege Escalation and SQL Injection30Monitor
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 | 7.6.30 | Package registry (OSV) |
| Packagist:typo3/cms-core | 8.7.17 | Package registry (OSV) |
| Packagist:typo3/cms-core | 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
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
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
osv
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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- HTTP Request SplittingCAPEC-105likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Format String InjectionCAPEC-135likelihood: High · High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/TYPO3-CMS/core/commit/854d03841b42123ab744c2591199b76ce65a8e45
- github.com/TYPO3-CMS/core/commit/aa4e270d04313fe7d8ea508a9c694db83875e981
- github.com/TYPO3-CMS/core/commit/dd0487bd8b4ec7204dbfff2b5812d797102a1778
- github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2018-07-12-2.yaml
- github.com/TYPO3-CMS/core
- typo3.org/security/advisory/typo3-core-sa-2018-002
Vendor advisories and official records. Exploit/PoC links are deliberately left out.