An XSS issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x before 1.37.2. The widthheight, widthheightpage, and nbytes properties of messages are not escaped when used in galleries or Special:RevisionDelete.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - An XSS issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x before 1.37.2.
    The widthheight, widthheightpage, and nbytes properties of messages are not escaped when used in galleries     or Special:RevisionDelete. (CVE-2022-28202)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote host is affected by the vulnerability described in GLSA-202305-24 (MediaWiki: Multiple Vulnerabilities)

  - MediaWiki before 1.36.2 allows XSS. Month related MediaWiki messages are not escaped before being used on     the Special:Search results page. (CVE-2021-41798)

  - MediaWiki before 1.36.2 allows a denial of service (resource consumption because of lengthy query     processing time). ApiQueryBacklinks (action=query&list=backlinks) can cause a full table scan.
    (CVE-2021-41799)

  - MediaWiki before 1.36.2 allows a denial of service (resource consumption because of lengthy query     processing time). Visiting Special:Contributions can sometimes result in a long running SQL query because     PoolCounter protection is mishandled. (CVE-2021-41800)

  - An issue was discovered in MediaWiki before 1.35.5, 1.36.x before 1.36.3, and 1.37.x before 1.37.1. The     REST API publicly caches results from private wikis. (CVE-2021-44854)

  - An issue was discovered in MediaWiki before 1.35.5, 1.36.x before 1.36.3, and 1.37.x before 1.37.1. There     is Blind Stored XSS via a URL to the Upload Image feature. (CVE-2021-44855)

  - An issue was discovered in MediaWiki before 1.35.5, 1.36.x before 1.36.3, and 1.37.x before 1.37.1. A     title blocked by AbuseFilter can be created via Special:ChangeContentModel due to the mishandling of the     EditFilterMergedContent hook return value. (CVE-2021-44856)

  - An issue was discovered in MediaWiki before 1.35.5, 1.36.x before 1.36.3, and 1.37.x before 1.37.1. It is     possible to use action=mcrundo followed by action=mcrrestore to replace the content of any arbitrary page     (that the user doesn't have edit rights for). This applies to any public wiki, or a private wiki that has     at least one page set in $wgWhitelistRead. (CVE-2021-44857)

  - An issue was discovered in MediaWiki before 1.35.5, 1.36.x before 1.36.3, and 1.37.x before 1.37.1. It is     possible to use action=edit&undo= followed by action=mcrundo and action=mcrrestore to view private pages     on a private wiki that has at least one page set in $wgWhitelistRead. (CVE-2021-44858)

  - An issue was discovered in MediaWiki before 1.35.5, 1.36.x before 1.36.3, and 1.37.x before 1.37.1. By     using an action=rollback query, attackers can view private wiki contents. (CVE-2021-45038)

  - An XSS issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x before 1.37.2.
    The widthheight, widthheightpage, and nbytes properties of messages are not escaped when used in galleries     or Special:RevisionDelete. (CVE-2022-28202)

  - An issue was discovered in MediaWiki through 1.37.1. The CentralAuth extension mishandles a ttl issue for     groups expiring in the future. (CVE-2022-28205)

  - An issue was discovered in MediaWiki through 1.37.1. ImportPlanValidator.php in the FileImporter extension     mishandles the check for edit rights. (CVE-2022-28206)

  - An issue was discovered in Mediawiki through 1.37.1. The check for the override-antispoof permission in     the AntiSpoof extension is incorrect. (CVE-2022-28209)

  - Guzzle, an extensible PHP HTTP client. `Authorization` headers on requests are sensitive information. In     affected versions when using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to     specify an `Authorization` header. On making a request which responds with a redirect to a URI with a     different origin (change in host, scheme or port), if we choose to follow it, we should remove the     `CURLOPT_HTTPAUTH` option before continuing, stopping curl from appending the `Authorization` header to     the new request. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected     users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix     was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added     Authorization header, however this earlier fix did not cover change in scheme or change in port. If you do     not require or expect redirects to be followed, one should simply disable redirects all together.
    Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl. (CVE-2022-31090)

  - Guzzle, an extensible PHP HTTP client. `Authorization` and `Cookie` headers on requests are sensitive     information. In affected versions on making a request which responds with a redirect to a URI with a     different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from     the request, before containing. Previously, we would only consider a change in host or scheme. Affected     Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series     of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle     7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this     earlier fix did not cover change in scheme or change in port. An alternative approach would be to use your     own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect     redirects to be followed, one should simply disable redirects all together. (CVE-2022-31091)

  - An issue was discovered in MediaWiki before 1.35.7, 1.36.x and 1.37.x before 1.37.3, and 1.38.x before     1.38.1. XSS can occur in configurations that allow a JavaScript payload in a username. After account     creation, when it sets the page title to Welcome followed by the username, the username is not escaped:
    SpecialCreateAccount::successfulAction() calls ::showSuccessPage() with a message as second parameter, and     OutputPage::setPageTitle() uses text(). (CVE-2022-34911)

  - An issue was discovered in MediaWiki before 1.37.3 and 1.38.x before 1.38.1. The contributions-title, used     on Special:Contributions, is used as page title without escaping. Hence, in a non-default configuration     where a username contains HTML entities, it won't be escaped. (CVE-2022-34912)

  - An issue was discovered in MediaWiki before 1.35.8, 1.36.x and 1.37.x before 1.37.5, and 1.38.x before     1.38.3. HTMLUserTextField exposes the existence of hidden users. (CVE-2022-41765)

  - An issue was discovered in MediaWiki before 1.35.8, 1.36.x and 1.37.x before 1.37.5, and 1.38.x before     1.38.3. When changes made by an IP address are reassigned to a user (using reassignEdits.php), the changes     will still be attributed to the IP address on Special:Contributions when doing a range lookup.
    (CVE-2022-41767)

  - An issue was discovered in MediaWiki before 1.35.9, 1.36.x through 1.38.x before 1.38.5, and 1.39.x before     1.39.1. When installing with a pre-existing data directory that has weak permissions, the SQLite files are     created with file mode 0644, i.e., world readable to local users. These files include credentials data.
    (CVE-2022-47927)

  - Mediawiki reports: (T316304, CVE-2022-41767) SECURITY: reassignEdits doesn't update results             in     an IP range check on Special:Contributions.. (T309894, CVE-2022-41765) SECURITY: HTMLUserTextField exposes     existence             of hidden users.  (T307278, CVE-2022-41766) SECURITY: On action=rollback the message     alreadyrolled can leak revision deleted user name. (CVE-2022-41766)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5246 advisory.

  - An issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x before 1.37.2. Users     with the editinterface permission can trigger infinite recursion, because a bare local interwiki is     mishandled for the mainpage message. (CVE-2022-28201)

  - An XSS issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x before 1.37.2.
    The widthheight, widthheightpage, and nbytes properties of messages are not escaped when used in galleries     or Special:RevisionDelete. (CVE-2022-28202)

  - A denial-of-service issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x     before 1.37.2. When many files exist, requesting Special:NewFiles with actor as a condition can result in     a very long running query. (CVE-2022-28203)

  - Guzzle is a PHP HTTP client. Guzzle prior to versions 6.5.6 and 7.4.3 contains a vulnerability with the     cookie middleware. The vulnerability is that it is not checked if the cookie domain equals the domain of     the server which sets the cookie via the Set-Cookie header, allowing a malicious server to set cookies for     unrelated domains. The cookie middleware is disabled by default, so most library consumers will not be     affected by this issue. Only those who manually add the cookie middleware to the handler stack or     construct the client with ['cookies' => true] are affected. Moreover, those who do not use the same Guzzle     client to call multiple domains and have disabled redirect forwarding are not affected by this     vulnerability. Guzzle versions 6.5.6 and 7.4.3 contain a patch for this issue. As a workaround, turn off     the cookie middleware. (CVE-2022-29248)

  - Guzzle is an open source PHP HTTP client. In affected versions the `Cookie` headers on requests are     sensitive information. On making a request using the `https` scheme to a server which responds with a     redirect to a URI with the `http` scheme, or on making a request to a server which responds with a     redirect to a a URI to a different host, we should not forward the `Cookie` header on. Prior to this fix,     only cookies that were managed by our cookie middleware would be safely removed, and any `Cookie` header     manually added to the initial request would not be stripped. We now always strip it, and allow the cookie     middleware to re-add any cookies that it deems should be there. Affected Guzzle 7 users should upgrade to     Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to     Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach to use your own     redirect middleware, rather than ours. If you do not require or expect redirects to be followed, one     should simply disable redirects all together. (CVE-2022-31042)

  - Guzzle is an open source PHP HTTP client. In affected versions `Authorization` headers on requests are     sensitive information. On making a request using the `https` scheme to a server which responds with a     redirect to a URI with the `http` scheme, we should not forward the `Authorization` header on. This is     much the same as to how we don't forward on the header if the host changes. Prior to this fix, `https` to     `http` downgrades did not result in the `Authorization` header being removed, only changes to the host.
    Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any     earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an     alternative approach which would be to use their own redirect middleware. Alternately users may simply     disable redirects all together if redirects are not expected or required. (CVE-2022-31043)

  - Guzzle, an extensible PHP HTTP client. `Authorization` headers on requests are sensitive information. In     affected versions when using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to     specify an `Authorization` header. On making a request which responds with a redirect to a URI with a     different origin (change in host, scheme or port), if we choose to follow it, we should remove the     `CURLOPT_HTTPAUTH` option before continuing, stopping curl from appending the `Authorization` header to     the new request. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected     users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix     was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added     Authorization header, however this earlier fix did not cover change in scheme or change in port. If you do     not require or expect redirects to be followed, one should simply disable redirects all together.
    Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl. (CVE-2022-31090)

  - Guzzle, an extensible PHP HTTP client. `Authorization` and `Cookie` headers on requests are sensitive     information. In affected versions on making a request which responds with a redirect to a URI with a     different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from     the request, before containing. Previously, we would only consider a change in host or scheme. Affected     Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series     of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle     7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this     earlier fix did not cover change in scheme or change in port. An alternative approach would be to use your     own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect     redirects to be followed, one should simply disable redirects all together. (CVE-2022-31091)

  - An issue was discovered in MediaWiki before 1.35.7, 1.36.x and 1.37.x before 1.37.3, and 1.38.x before     1.38.1. XSS can occur in configurations that allow a JavaScript payload in a username. After account     creation, when it sets the page title to Welcome followed by the username, the username is not escaped:
    SpecialCreateAccount::successfulAction() calls ::showSuccessPage() with a message as second parameter, and     OutputPage::setPageTitle() uses text(). (CVE-2022-34911)

  - An issue was discovered in MediaWiki before 1.37.3 and 1.38.x before 1.38.1. The contributions-title, used     on Special:Contributions, is used as page title without escaping. Hence, in a non-default configuration     where a username contains HTML entities, it won't be escaped. (CVE-2022-34912)

  - Mediawiki reports: (T292763. CVE-2021-44854) REST API incorrectly publicly caches             autocomplete     search results from private wikis. (T271037, CVE-2021-44856) Title blocked in AbuseFilter can be created     via             Special:ChangeContentModel. (T297322, CVE-2021-44857) Unauthorized users can use     action=mcrundo to             replace the content of arbitrary pages.  (T297322, CVE-2021-44858)     Unauthorized users can view contents of private             wikis using various actions. (T297574,     CVE-2021-45038) Unauthorized users can access private wiki             contents using rollback action     (T293589, CVE-2021-44855) Blind Stored XSS in VisualEditor media dialog. (T294686) Special:Nuke doesn't     actually delete pages. (CVE-2021-44854, CVE-2021-44855, CVE-2021-44856)

  - Mediawiki reports: (T316304, CVE-2022-41767) SECURITY: reassignEdits doesn't update results             in     an IP range check on Special:Contributions.. (T309894, CVE-2022-41765) SECURITY: HTMLUserTextField exposes     existence             of hidden users.  (T307278, CVE-2022-41766) SECURITY: On action=rollback the message     alreadyrolled can leak revision deleted user name. (CVE-2022-41765, CVE-2022-41767)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3117 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-3117-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                      Markus Koschany     September 22, 2022                            https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : mediawiki     Version        : 1:1.31.16-1+deb10u3     CVE ID         : CVE-2021-44856 CVE-2022-28201 CVE-2022-28202 CVE-2022-28203                      CVE-2022-34911 CVE-2022-34912

    Several security vulnerabilities were discovered in mediawiki, a website engine     for collaborative work. Insufficiently escaped input text may allow a malicious     user to perform cross-site-scripting (XSS) attacks.

    For Debian 10 buster, these problems have been fixed in version     1:1.31.16-1+deb10u3.

    We recommend that you upgrade your mediawiki packages.

    For the detailed security status of mediawiki please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/mediawiki

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: This is a digitally signed message part

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 79ea6066-b40e-11ec-8b93-080027b24e86 advisory.

  - An XSS issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x before 1.37.2.
    The widthheight, widthheightpage, and nbytes properties of messages are not escaped when used in galleries     or Special:RevisionDelete. (CVE-2022-28202)

  - An issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x before 1.37.2. Users     with the editinterface permission can trigger infinite recursion, because a bare local interwiki is     mishandled for the mainpage message. (CVE-2022-28201)

  - A denial-of-service issue was discovered in MediaWiki before 1.35.6, 1.36.x before 1.36.4, and 1.37.x     before 1.37.2. When many files exist, requesting Special:NewFiles with actor as a condition can result in     a very long running query. (CVE-2022-28203)

  - A denial-of-service issue was discovered in MediaWiki 1.37.x before 1.37.2. Rendering of     w/index.php?title=Special%3AWhatLinksHere&target=Property%3AP31&namespace=1&invert=1 can take more than     thirty seconds. There is a DDoS risk. (CVE-2022-28204)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
247670	Linux Distros Unpatched Vulnerability : CVE-2022-28202	Nessus	Misc.	medium
176192	GLSA-202305-24 : MediaWiki: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	critical
165710	Debian DSA-5246-1 : mediawiki - security update	Nessus	Debian Local Security Checks	high
165431	Debian dla-3117 : mediawiki - security update	Nessus	Debian Local Security Checks	medium
159495	FreeBSD : mediawiki -- multiple vulnerabilities (79ea6066-b40e-11ec-8b93-080027b24e86)	Nessus	FreeBSD Local Security Checks	medium

Detections

Analytics

CVE-2022-28202

medium

Tenable Plugins

medium

critical

high

medium

medium