Ruby-saml before 1.3.0 allows attackers to perform XML signature wrapping attacks via unspecified vectors.
Weakness
The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Ruby-saml |
Onelogin |
* |
1.2.0 (including) |
| Ruby-saml |
Ubuntu |
artful |
* |
| Ruby-saml |
Ubuntu |
esm-apps/xenial |
* |
| Ruby-saml |
Ubuntu |
upstream |
* |
| Ruby-saml |
Ubuntu |
wily |
* |
| Ruby-saml |
Ubuntu |
xenial |
* |
| Ruby-saml |
Ubuntu |
yakkety |
* |
| Ruby-saml |
Ubuntu |
zesty |
* |
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.
References