Skip to content

GHSA-q68v-vcjg-r3vp CVE-2012-1607

TYPO3 allows remote attackers to obtain the database name via a direct request

Medium Packagist
Severity
Medium
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
3.09%
Chance of exploitation in the next 30 days. Higher than 87.72% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
None yet
No fixed version published

Description

The Command Line Interface (CLI) script in TYPO3 4.4.0 through 4.4.13, 4.5.0 through 4.5.13, 4.6.0 through 4.6.6, 4.7, and 6.0 allows remote attackers to obtain the database name via a direct request.

Affected versions

Packagist

PackageVulnerableFixed in
typo3/cms
>= 4.4.0, <= 4.4.13
No fix yet
typo3/cms
>= 4.5.0, <= 4.5.13
No fix yet
typo3/cms
>= 4.6.0, <= 4.6.6
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

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