Skip to content

GHSA-5vj8-g3qg-4qh6 BIT-mediawiki-2023-29141 CVE-2023-29141

X-Forwarded-For header allows brute-forcing autoblocked IP addresses

Critical Packagist
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
1.19%
Chance of exploitation in the next 30 days. Higher than 68.04% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Fix
1.39.3
Upgrade mediawiki/core to this version or later

Description

An issue was discovered in MediaWiki before 1.35.10, 1.36.x through 1.38.x before 1.38.6, and 1.39.x before 1.39.3. An auto-block can occur for an untrusted X-Forwarded-For header.

Affected versions

Packagist

PackageVulnerableFixed in
mediawiki/core
>= 1.39.0, < 1.39.3
1.39.3
mediawiki/core
>= 1.38.0, < 1.38.6
1.38.6
mediawiki/core
< 1.35.10
1.35.10

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.39.3

composer
composer require mediawiki/core:^1.39.3

Severity breakdown

CVSS 3.1 9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

How to prevent it
  • Implementation: Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].
  • Implementation: Use only SSL communication.
  • Implementation: Terminate the client session after each request.
  • System Configuration: Turn all pages to non-cacheable.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-w5fx-cx7f-6vr9
MediaWiki Denial of Service vulnerability
High 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
GHSA-rj9p-8jxj-2ch4
MediaWiki Cross-site Scripting (XSS) vulnerability
Medium Also affects mediawiki/core
Is this in your code?

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