CVE Vulnerabilities

CVE-2013-4549

Improper Input Validation

Published: Dec 23, 2013 | Modified: Feb 13, 2023
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
4.3 MODERATE
AV:N/AC:M/Au:N/C:N/I:N/A:P
RedHat/V3
Ubuntu
MEDIUM

QXmlSimpleReader in Qt before 5.2 allows context-dependent attackers to cause a denial of service (memory consumption) via an XML Entity Expansion (XEE) attack.

Weakness

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.

Affected Software

Name Vendor Start Version End Version
Qt Digia * 5.1.0 (including)
Qt Qt 5.0.0 (including) 5.0.0 (including)
Qt Qt 5.0.1 (including) 5.0.1 (including)
Qt Qt 5.0.2 (including) 5.0.2 (including)
Phantomjs Ubuntu artful *
Phantomjs Ubuntu quantal *
Phantomjs Ubuntu raring *
Phantomjs Ubuntu saucy *
Phantomjs Ubuntu trusty *
Phantomjs Ubuntu trusty/esm *
Phantomjs Ubuntu upstream *
Phantomjs Ubuntu utopic *
Phantomjs Ubuntu vivid *
Phantomjs Ubuntu wily *
Phantomjs Ubuntu yakkety *
Phantomjs Ubuntu zesty *
Qt4-x11 Ubuntu artful *
Qt4-x11 Ubuntu bionic *
Qt4-x11 Ubuntu cosmic *
Qt4-x11 Ubuntu devel *
Qt4-x11 Ubuntu disco *
Qt4-x11 Ubuntu esm-apps/bionic *
Qt4-x11 Ubuntu esm-infra/xenial *
Qt4-x11 Ubuntu lucid *
Qt4-x11 Ubuntu precise *
Qt4-x11 Ubuntu quantal *
Qt4-x11 Ubuntu raring *
Qt4-x11 Ubuntu saucy *
Qt4-x11 Ubuntu trusty *
Qt4-x11 Ubuntu trusty/esm *
Qt4-x11 Ubuntu upstream *
Qt4-x11 Ubuntu utopic *
Qt4-x11 Ubuntu vivid *
Qt4-x11 Ubuntu wily *
Qt4-x11 Ubuntu xenial *
Qt4-x11 Ubuntu yakkety *
Qt4-x11 Ubuntu zesty *
Qtbase-opensource-src Ubuntu artful *
Qtbase-opensource-src Ubuntu bionic *
Qtbase-opensource-src Ubuntu cosmic *
Qtbase-opensource-src Ubuntu devel *
Qtbase-opensource-src Ubuntu disco *
Qtbase-opensource-src Ubuntu esm-infra/bionic *
Qtbase-opensource-src Ubuntu esm-infra/xenial *
Qtbase-opensource-src Ubuntu raring *
Qtbase-opensource-src Ubuntu saucy *
Qtbase-opensource-src Ubuntu trusty *
Qtbase-opensource-src Ubuntu upstream *
Qtbase-opensource-src Ubuntu utopic *
Qtbase-opensource-src Ubuntu vivid *
Qtbase-opensource-src Ubuntu vivid/stable-phone-overlay *
Qtbase-opensource-src Ubuntu wily *
Qtbase-opensource-src Ubuntu xenial *
Qtbase-opensource-src Ubuntu yakkety *
Qtbase-opensource-src Ubuntu zesty *

Extended Description

Input validation is a frequently-used technique for checking potentially dangerous inputs in order to ensure that the inputs are safe for processing within the code, or when communicating with other components. When software does not validate input properly, an attacker is able to craft the input in a form that is not expected by the rest of the application. This will lead to parts of the system receiving unintended input, which may result in altered control flow, arbitrary control of a resource, or arbitrary code execution. Input validation is not the only technique for processing input, however. Other techniques attempt to transform potentially-dangerous input into something safe, such as filtering (CWE-790) - which attempts to remove dangerous inputs - or encoding/escaping (CWE-116), which attempts to ensure that the input is not misinterpreted when it is included in output to another component. Other techniques exist as well (see CWE-138 for more examples.) Input validation can be applied to:

Data can be simple or structured. Structured data can be composed of many nested layers, composed of combinations of metadata and raw data, with other simple or structured data. Many properties of raw data or metadata may need to be validated upon entry into the code, such as:

Implied or derived properties of data must often be calculated or inferred by the code itself. Errors in deriving properties may be considered a contributing factor to improper input validation.

Note that “input validation” has very different meanings to different people, or within different classification schemes. Caution must be used when referencing this CWE entry or mapping to it. For example, some weaknesses might involve inadvertently giving control to an attacker over an input when they should not be able to provide an input at all, but sometimes this is referred to as input validation. Finally, it is important to emphasize that the distinctions between input validation and output escaping are often blurred, and developers must be careful to understand the difference, including how input validation is not always sufficient to prevent vulnerabilities, especially when less stringent data types must be supported, such as free-form text. Consider a SQL injection scenario in which a person’s last name is inserted into a query. The name “O’Reilly” would likely pass the validation step since it is a common last name in the English language. However, this valid name cannot be directly inserted into the database because it contains the “’” apostrophe character, which would need to be escaped or otherwise transformed. In this case, removing the apostrophe might reduce the risk of SQL injection, but it would produce incorrect behavior because the wrong name would be recorded.

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Even though client-side checks provide minimal benefits with respect to server-side security, they are still useful. First, they can support intrusion detection. If the server receives input that should have been rejected by the client, then it may be an indication of an attack. Second, client-side error-checking can provide helpful feedback to the user about the expectations for valid input. Third, there may be a reduction in server-side processing time for accidental input errors, although this is typically a small savings.
  • Inputs should be decoded and canonicalized to the application’s current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174). Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked. Use libraries such as the OWASP ESAPI Canonicalization control.
  • Consider performing repeated canonicalization until your input does not change any more. This will avoid double-decoding and similar scenarios, but it might inadvertently modify inputs that are allowed to contain properly-encoded dangerous content.

References