Skip to content

melisplatform/melis-front vulnerable to deserialization of untrusted data

High severity GitHub Reviewed Published Oct 11, 2022 in melisplatform/melis-front • Updated Jan 27, 2023

Package

composer melisplatform/melis-front (Composer)

Affected versions

< 5.0.1

Patched versions

5.0.1

Description

Impact

Attackers can deserialize arbitrary data on affected versions of melisplatform/melis-front, and ultimately leads to the execution of arbitrary PHP code on the system. Conducting this attack does not require authentication.

Users should immediately upgrade to melisplatform/melis-front >= 5.0.1.

Patches

This issue was addressed by restricting allowed classes when deserializing user-controlled data.

References

For more information

If you have any questions or comments about this advisory, you can contact:

  • The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
  • The maintainers, by opening an issue on this repository.

References

@sgris sgris published to melisplatform/melis-front Oct 11, 2022
Published to the GitHub Advisory Database Oct 11, 2022
Reviewed Oct 11, 2022
Published by the National Vulnerability Database Oct 12, 2022
Last updated Jan 27, 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
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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:H/PR:N/UI:N/S:U/C:H/I:H/A:L

EPSS score

0.289%
(69th percentile)

Weaknesses

CVE ID

CVE-2022-39298

GHSA ID

GHSA-h479-2mv4-5c26

Source code

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