Microsoft Azure Monitor Agent code injection

Summaryinfo

A vulnerability has been found in Microsoft Azure Monitor Agent and classified as critical. This issue affects some unknown processing. This manipulation causes code injection. This vulnerability is handled as CVE-2025-47988. The attack can only be done within the local network. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability classified as critical was found in Microsoft Azure Monitor Agent (the affected version unknown). Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Improper control of generation of code ('code injection') in Azure Monitor Agent allows an unauthorized attacker to execute code over an adjacent network.

The weakness was released 07/08/2025 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. This vulnerability is known as CVE-2025-47988. The exploitation appears to be difficult. The attack needs to be done within the local network. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/23/2025). The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 241557 (Microsoft Azure Monitor Agent < 1.35.1 Remote Code Execution (CVE-2025-47988)), which helps to determine the existence of the flaw in a target environment.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (241557) and EUVD (EUVD-2025-20534). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Cloud Software

Vendor

• Microsoft

Name

• Azure Monitor Agent

License

• commercial

Website

• Vendor: https://www.microsoft.com/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion