Apache VCL up to 2.1/2.2.1/2.3.1 Web GUI/XMLRPC API input validation

Summaryinfo

A vulnerability was found in Apache VCL up to 2.1/2.2.1/2.3.1. It has been rated as critical. This issue affects some unknown processing of the component Web GUI/XMLRPC API. The manipulation leads to input validation. This vulnerability is referenced as CVE-2013-0267. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Apache VCL up to 2.1/2.2.1/2.3.1. This issue affects an unknown function of the component Web GUI/XMLRPC API. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The Privileges portion of the web GUI and the XMLRPC API in Apache VCL 2.3.x before 2.3.2, 2.2.x before 2.2.2 and 2.1 allow remote authenticated users with nodeAdmin, manageGroup, resourceGrant, or userGrant permissions to gain privileges, cause a denial of service, or conduct cross-site scripting (XSS) attacks by leveraging improper data validation.

The bug was discovered 05/06/2013. The weakness was published 02/21/2018 (Website). The advisory is shared at mail-archives.apache.org. The identification of this vulnerability is CVE-2013-0267 since 12/06/2012. The attack may be initiated remotely. The successful exploitation requires a simple authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 1752 days. During that time the estimated underground price was around $5k-$25k.

Upgrading to version 2.2.2 or 2.3.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at OSVDB (93008†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Apache

Name

• VCL

Version

• 2.0
• 2.1
• 2.2.0
• 2.2.1
• 2.3.0
• 2.3.1

License

• open-source

Website

• Vendor: https://www.apache.org/
• Product: https://github.com/apache/vcl/

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