Contao up to 4.9.39/4.13.20/5.1.3 AJAX Request path traversal

Summaryinfo

A vulnerability marked as critical has been reported in Contao up to 4.9.39/4.13.20/5.1.3. Affected is an unknown function of the component AJAX Request Handler. This manipulation causes path traversal. This vulnerability appears as CVE-2023-29200. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Contao up to 4.9.39/4.13.20/5.1.3. Affected by this vulnerability is an unknown code of the component AJAX Request Handler. The manipulation with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality. The summary by CVE is:

Contao is an open source content management system. Prior to versions 4.9.40, 4.13.21, and 5.1.4, logged in users can list arbitrary system files in the file manager by manipulating the Ajax request. However, it is not possible to read the contents of these files. Users should update to Contao 4.9.40, 4.13.21 or 5.1.4 to receive a patch. There are no known workarounds.

The weakness was presented 04/25/2023 as GHSA-fp7q-xhhw-6rj3. The advisory is shared at github.com. This vulnerability is known as CVE-2023-29200 since 04/03/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 4.9.40, 4.13.21 or 5.1.4 eliminates this vulnerability. Applying the patch 6f3e705f4ff23f4419563d09d8485793569f31df is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Contao

Version

• 4.9.0
• 4.9.1
• 4.9.2
• 4.9.3
• 4.9.4
• 4.9.5
• 4.9.6
• 4.9.7
• 4.9.8
• 4.9.9
• 4.9.10
• 4.9.11
• 4.9.12
• 4.9.13
• 4.9.14
• 4.9.15
• 4.9.16
• 4.9.17
• 4.9.18
• 4.9.19
• 4.9.20
• 4.9.21
• 4.9.22
• 4.9.23
• 4.9.24
• 4.9.25
• 4.9.26
• 4.9.27
• 4.9.28
• 4.9.29
• 4.9.30
• 4.9.31
• 4.9.32
• 4.9.33
• 4.9.34
• 4.9.35
• 4.9.36
• 4.9.37
• 4.9.38
• 4.9.39
• 4.13.0
• 4.13.1
• 4.13.2
• 4.13.3
• 4.13.4
• 4.13.5
• 4.13.6
• 4.13.7
• 4.13.8
• 4.13.9
• 4.13.10
• 4.13.11
• 4.13.12
• 4.13.13
• 4.13.14
• 4.13.15
• 4.13.16
• 4.13.17
• 4.13.18
• 4.13.19
• 4.13.20
• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3

License

• open-source

Website

• Product: https://github.com/contao/contao/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion