TYPO3 CVE-2019-19850 SQL Injection Vulnerability

Description

TYPO3 is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data before using it in an SQL query. Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. Versions prior to TYPO3 8.7.30, 9.5.12 and 10.2.2 are vulnerable.

Technologies Affected

• Typo3 Typo3 10.0.0
• Typo3 Typo3 10.2.0
• Typo3 Typo3 8.0.0
• Typo3 Typo3 8.0.1
• Typo3 Typo3 8.1.0
• Typo3 Typo3 8.1.1
• Typo3 Typo3 8.1.2
• Typo3 Typo3 8.2.0
• Typo3 Typo3 8.2.1
• Typo3 Typo3 8.3.0
• Typo3 Typo3 8.3.1
• Typo3 Typo3 8.4.0
• Typo3 Typo3 8.4.1
• Typo3 Typo3 8.5.0
• Typo3 Typo3 8.5.1
• Typo3 Typo3 8.6.0
• Typo3 Typo3 8.6.1
• Typo3 Typo3 8.7.0
• Typo3 Typo3 8.7.1
• Typo3 Typo3 8.7.2
• Typo3 Typo3 8.7.20
• Typo3 Typo3 8.7.21
• Typo3 Typo3 8.7.22
• Typo3 Typo3 8.7.23
• Typo3 Typo3 8.7.24
• Typo3 Typo3 8.7.25
• Typo3 Typo3 8.7.26
• Typo3 Typo3 8.7.27
• Typo3 Typo3 8.7.29
• Typo3 Typo3 8.7.3
• Typo3 Typo3 8.7.4
• Typo3 Typo3 8.7.5
• Typo3 Typo3 9.0.0
• Typo3 Typo3 9.3.3
• Typo3 Typo3 9.4.0
• Typo3 Typo3 9.5
• Typo3 Typo3 9.5.10
• Typo3 Typo3 9.5.11
• Typo3 Typo3 9.5.2
• Typo3 Typo3 9.5.4
• Typo3 Typo3 9.5.5
• Typo3 Typo3 9.5.6
• Typo3 Typo3 9.5.7
• Typo3 Typo3 9.5.8

Recommendations

Block external access at the network boundary, unless external parties require service.
If global access isn’t needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.

Run all software as a nonprivileged user with minimal access rights.
To limit the consequences of successful exploits, run server processes within a restricted environment using facilities such as chroot or jail.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity including unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.

Modify default ACL settings.
Implement database access control to limit the immediate impact of such vulnerabilities on the data within the database and possibly the database itself. Ensure that applications are isolated from one another and from sensitive data in the database through separate user accounts and restrictive ACL configurations

Updates are available. Please see the references or vendor advisory for more information.