GHSA-27fw-r78j-h898 CVE-2019-12466
Wikimedia MediaWiki allows CSRF
High
Packagist
- Severity
- 8.8 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 0.84%
- Chance of exploitation in the next 30 days. Higher than 57.98% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-352 Cross-Site Request Forgery (CSRF)
- Fix
1.27.6- Upgrade mediawiki/core to this version or later
Description
Wikimedia MediaWiki through 1.32.1 allows CSRF in logout feature.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| mediawiki/core | >= 1.27.0, < 1.27.6 |
1.27.6 |
| mediawiki/core | >= 1.30.0, < 1.30.2 |
1.30.2 |
| mediawiki/core | >= 1.31.0, < 1.31.2 |
1.31.2 |
| mediawiki/core | >= 1.32.0, < 1.32.2 |
1.32.2 |
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.
mediawiki/core Packagist → 1.27.6
- composer
composer require mediawiki/core:^1.27.6
Severity breakdown
CVSS 3.0 8.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-352: Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Implementation: Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Architecture and Design: Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
- Architecture and Design: Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
- Architecture and Design: Use the "double-submitted cookie" method as described by Felten and Zeller: When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same. Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult. This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
- Architecture and Design: Do not use the GET method for any request that triggers a state change.
- Implementation: Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-w5fx-cx7f-6vr9 MediaWiki Denial of Service vulnerability | High | Also affects mediawiki/core |
| GHSA-5vj8-g3qg-4qh6 X-Forwarded-For header allows brute-forcing autoblocked IP addresses | Critical | Also affects mediawiki/core |
| GHSA-c8wv-qwwc-6j73 MediaWiki allows a denial of service | Medium | Also affects mediawiki/core |
| GHSA-rqvj-fc2x-99q6 OATHAuth extension in MediaWiki is not implementing rate limit | High | Also affects mediawiki/core |
| GHSA-c4rj-wrmq-52rj MediaWiki Special:UserRights exposes the existence of hidden users | Medium | Also affects mediawiki/core |
| GHSA-h8qx-mj6v-2934 MediaWiki Cross-site Scripting (XSS) vulnerability | Medium | Also affects mediawiki/core |
| GHSA-4vr7-m8p8-434h MediaWiki Cross-site Scripting (XSS) vulnerability | Medium | Also affects mediawiki/core |
| GHSA-2f58-vf6g-6p8x MediaWiki Cross-site Scripting (XSS) vulnerability | Medium | Also affects mediawiki/core |
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