GHSA-5qp6-78pr-gv8c CVE-2013-4701
PHP OpenID Library Denial of Service vulnerability
High
Packagist
- Severity
- High
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 3.00%
- Chance of exploitation in the next 30 days. Higher than 87.35% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 2 packages have a fixed version
Description
Auth/Yadis/XML.php in PHP OpenID Library 2.2.2 and earlier allows remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service (CPU and memory consumption) via XRDS data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| openid/php-openid | < 2.3.0 |
2.3.0 |
| typo3/cms | >= 6.2.0, < 6.2.6 |
6.2.6 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
openid/php-openid Packagist → 2.3.0
- composer
composer require openid/php-openid:^2.3.0
typo3/cms Packagist → 6.2.6
- composer
composer require typo3/cms:^6.2.6
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
- github.com/openid/php-openid/commit/625c16bb28bb120d262b3f19f89c2c06cb9b0da9
- github.com/FriendsOfPHP/security-advisories/blob/master/openid/php-openid/CVE-2…
- github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2013-4701…
- typo3.org/security/advisory/typo3-core-sa-2014-002
- jvn.jp/en/jp/JVN24713981/index.html
- jvndb.jvn.jp/jvndb/JVNDB-2013-000080
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00028.html
- lists.opensuse.org/opensuse-updates/2016-08/msg00083.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-f3wf-q4fj-3gxf TYPO3 Denial of Service in Online Media Asset Handling | Medium | Also affects typo3/cms |
| GHSA-6487-3qvg-8px9 TYPO3 Information Disclosure in Install Tool | Medium | Also affects typo3/cms |
| GHSA-f777-f784-36gm TYPO3 Security Misconfiguration in Install Tool Cookie | High | Also affects typo3/cms |
| GHSA-2rcw-9hrm-8q7q TYPO3 Cross-Site Scripting in Frontend User Login | Medium | Also affects typo3/cms |
| GHSA-7q33-hxwj-7p8v TYPO3 Cross-Site Scripting in Backend Modal Component | Medium | Also affects typo3/cms |
| GHSA-8m6j-p5jv-v69w TYPO3 Cross-Site Scripting in Online Media Asset Rendering | Medium | Also affects typo3/cms |
| GHSA-8h4m-r4wm-xj7r TYPO3 Arbitrary Code Execution via File List Module | High | Also affects typo3/cms |
| GHSA-g585-crjf-vhwq TYPO3 Denial of Service in Frontend Record Registration | High | Also affects typo3/cms |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor