CVE-2012-3527
published 2012-09-05CVE-2012-3527: view_help.php in the backend help system in TYPO3 4.5.x before 4.5.19, 4.6.x before 4.6.12 and 4.7.x before 4.7.4 allows remote authenticated backend users to…
PriorityP429medium4.6CVSS 2.0
AVNACHAuSCPIPAP
EPSS
2.12%
79.6th percentile
view_help.php in the backend help system in TYPO3 4.5.x before 4.5.19, 4.6.x before 4.6.12 and 4.7.x before 4.7.4 allows remote authenticated backend users to unserialize arbitrary objects and possibly execute arbitrary PHP code via an unspecified parameter, related to a "missing signature (HMAC)."
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| typo3 | cms | >= 4.5.0 < 4.5.19 | 4.5.19 |
| typo3 | cms | >= 4.6.0 < 4.6.12 | 4.6.12 |
| typo3 | cms | >= 4.7.0 < 4.7.4 | 4.7.4 |
| typo3 | typo3 | >= 4.5.0 < 4.5.19 | 4.5.19 |
| typo3 | typo3 | >= 4.6.0 < 4.6.12 | 4.6.12 |
| typo3 | typo3 | >= 4.7.0 < 4.7.4 | 4.7.4 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
TYPO3 allows remote authenticated backend users to unserialize arbitrary objects
osv·2022-05-17
CVE-2012-3527 [MEDIUM] TYPO3 allows remote authenticated backend users to unserialize arbitrary objects
TYPO3 allows remote authenticated backend users to unserialize arbitrary objects
view_help.php in the backend help system in TYPO3 4.5.x before 4.5.19, 4.6.x before 4.6.12 and 4.7.x before 4.7.4 allows remote authenticated backend users to unserialize arbitrary objects and possibly execute arbitrary PHP code via an unspecified parameter, related to a "missing signature (HMAC)."
GHSA
TYPO3 allows remote authenticated backend users to unserialize arbitrary objects
ghsa·2022-05-17
CVE-2012-3527 [MEDIUM] CWE-502 TYPO3 allows remote authenticated backend users to unserialize arbitrary objects
TYPO3 allows remote authenticated backend users to unserialize arbitrary objects
view_help.php in the backend help system in TYPO3 4.5.x before 4.5.19, 4.6.x before 4.6.12 and 4.7.x before 4.7.4 allows remote authenticated backend users to unserialize arbitrary objects and possibly execute arbitrary PHP code via an unspecified parameter, related to a "missing signature (HMAC)."
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
CWE
Improperly Controlled Modification of Dynamically-Determined Object Attributes
mitre_cwe
CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes
The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
If the object contains attributes that were only intended for internal use, then their unexpected modification could lead to a vulnerability. This weakness is sometimes known by the language-specific mechanisms that make it possible, such as mass assignment, autobinding, or object injection.
Modes of Introduction:
Phase: Architecture and Design
Phase: Implementation
Common Consequences:
Scope: Integrity. Impact: Modify Application Data. An attacker could modify sensitive d
CWE
Deserialization of Untrusted Data
mitre_cwe
CWE-502 Deserialization of Untrusted Data
CWE-502: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Background: Serialization and deserialization refer to the process of taking program-internal object-related data, packaging it in a way that allows the data to be externally stored or transferred ("serialization"), then extracting the serialized data to reconstruct the original object ("deserialization").
Modes of Introduction:
Phase: Architecture and Design
Note: OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.
Phase: Implementation
Common Consequences:
Scope: Integrity. Impact: Modify Application Data, Unexpected State. Attackers can modify unexpected objects or data that was as
http://osvdb.org/84773http://secunia.com/advisories/50287http://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2012-004/http://www.debian.org/security/2012/dsa-2537http://www.openwall.com/lists/oss-security/2012/08/22/8https://exchange.xforce.ibmcloud.com/vulnerabilities/77791http://osvdb.org/84773http://secunia.com/advisories/50287http://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2012-004/http://www.debian.org/security/2012/dsa-2537http://www.openwall.com/lists/oss-security/2012/08/22/8https://exchange.xforce.ibmcloud.com/vulnerabilities/77791
2012-09-05
Published