Skip to content

GHSA-rwx5-7x5r-jgrm CVE-2011-4900

Typo3 Information Disclosure

Medium Packagist
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.95%
Chance of exploitation in the next 30 days. Higher than 61.35% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
4.5.4
Upgrade typo3/cms to this version or later

Description

TYPO3 before 4.5.4 allows Information Disclosure in the backend.

Affected versions

Packagist

PackageVulnerableFixed in
typo3/cms
< 4.5.4
4.5.4

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

typo3/cms Packagist → 4.5.4

composer
composer require typo3/cms:^4.5.4

Severity breakdown

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-f3wf-q4fj-3gxf
TYPO3 Denial of Service in Online Media Asset Handling
Medium Also affects typo3/cms
GHSA-6487-3qvg-8px9
TYPO3 Information Disclosure in Install Tool
Medium Also affects typo3/cms
GHSA-f777-f784-36gm
TYPO3 Security Misconfiguration in Install Tool Cookie
High Also affects typo3/cms
GHSA-2rcw-9hrm-8q7q
TYPO3 Cross-Site Scripting in Frontend User Login
Medium Also affects typo3/cms
GHSA-7q33-hxwj-7p8v
TYPO3 Cross-Site Scripting in Backend Modal Component
Medium Also affects typo3/cms
GHSA-8m6j-p5jv-v69w
TYPO3 Cross-Site Scripting in Online Media Asset Rendering
Medium Also affects typo3/cms
GHSA-8h4m-r4wm-xj7r
TYPO3 Arbitrary Code Execution via File List Module
High Also affects typo3/cms
GHSA-g585-crjf-vhwq
TYPO3 Denial of Service in Frontend Record Registration
High Also affects typo3/cms
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor