Skip to content

GHSA-4r76-xr68-w7m7

TYPO3 may allow editors to change, create, or delete metadata of files not within their file mounts

High Packagist
Severity
8.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-269 Improper Privilege Management
Fix
6.2.14
Upgrade typo3/cms to this version or later

Description

It has been discovered, that editors with access to file meta data table could change, create or delete metadata of files which are not within their file mounts.

Affected versions

Packagist

PackageVulnerableFixed in
typo3/cms
>= 6.2.0, < 6.2.14
6.2.14
typo3/cms
>= 7.0.0, < 7.3.1
7.3.1

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 → 6.2.14

composer
composer require typo3/cms:^6.2.14

Severity breakdown

CVSS 3.1 8.8

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

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

Weakness

CWE-269: Improper Privilege Management

The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system.
  • Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

References

Timeline

  1. Published
  2. Last updated by the source
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