Skip to content

Test code in published microsoft-graph-core package exposes phpinfo()

Moderate
MIchaelMainer published GHSA-mhhp-c3cm-2r86 Dec 5, 2023

Package

composer microsoft-graph-core (Composer)

Affected versions

<= 2.0.1

Patched versions

2.0.2

Description

Impact

The Microsoft Graph Core PHP SDK published packages which contained test code that enabled the use of the phpInfo() function from any application that could access and execute the file at vendor/microsoft/microsoft-graph-core/tests/GetPhpInfo.php. The phpInfo function exposes system information.

The vulnerability affects the GetPhpInfo.php script of the PHP SDK which contains a call to the phpinfo() function.

This vulnerability requires a misconfiguration of the server to be present so it can be exploited. For example, making the PHP application’s /vendor directory web accessible.

The combination of the vulnerability and the server misconfiguration would allow an attacker to craft an HTTP request that executes the phpinfo() method. The attacker would then be able to get access to system information like configuration, modules, and environment variables and later on use the compromised secrets to access additional data.

Patches

This problem has been patched in version 2.0.2.

Workarounds

If an immediate deployment with the updated vendor package is not available, you can perform the following temporary workarounds:

  • delete the vendor/microsoft/microsoft-graph-core/tests/GetPhpInfo.php file
  • remove access to the /vendor directory will remove this vulnerability
  • disable the phpinfo function

References

For more information about the vulnerability and the patch, users can refer to the following sources:

Severity

Moderate

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
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:N/UI:N/S:U/C:L/I:N/A:N

CVE ID

CVE-2023-49283

Weaknesses