Skip to content

Phar unserialization vulnerability in phpMussel

High severity GitHub Reviewed Published Jun 10, 2020 in phpMussel/phpMussel • Updated Feb 16, 2023

Package

composer Maikuolan/phpMussel (Composer)

Affected versions

>= 1.0.0, < 1.6.0

Patched versions

1.6.0
composer phpmussel/phpmussel (Composer)
>= 1.0.0, < 1.6.0
1.6.0

Description

Impact

What kind of vulnerability is it? Who is impacted?

Anyone using >= v1.0.0 < v1.6.0.

Patches

Has the problem been patched? What versions should users upgrade to?

Yes. Upgrading to at least >= v1.6.0 (the earliest safe version) will resolve the problem. However, as multiple new major versions have been released since that version, upgrading to the latest available version is recommended, in order to protect against any potential future vulnerabilities, unknown at the time of writing this advisory.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Yes. In the package's configuration, disable archive checking by setting check_archives to false (thus avoiding execution of the affected parts of the codebase entirely).

References

Are there any links users can visit to find out more?

Yes. The vulnerability is documented at SECURITY.md and also at #167.

For more information

If you have any questions or comments about this advisory:

References

@Maikuolan Maikuolan published to phpMussel/phpMussel Jun 10, 2020
Reviewed Jun 10, 2020
Published to the GitHub Advisory Database Jun 10, 2020
Last updated Feb 16, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N

EPSS score

0.343%
(72nd percentile)

Weaknesses

CVE ID

CVE-2020-4043

GHSA ID

GHSA-qr95-4mq5-r3fh

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.