LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40497: Wazuh v3.6.1 - v3.13.5, v4.0.0 - v4.2.7, and v4.3.0 - v4.3.7 were discovered to contain an authenticated re...

Wazuh v3.6.1 - v3.13.5, v4.0.0 - v4.2.7, and v4.3.0 - v4.3.7 were discovered to contain an authenticated remote code execution (RCE) vulnerability via the Active Response endpoint.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is an authenticated remote code execution flaw in Wazuh’s Active Response endpoint. A user with low privileges could potentially run code on affected Wazuh systems. For executives, the concern is compromise of a security monitoring platform, which can weaken detection and response operations.

Executive priority

Treat this as a high-priority security platform risk. It does not have cited active exploitation here, but authenticated RCE in a monitoring tool can create outsized business impact if an internal account is compromised.

Technical view

CVE-2022-40497 is a CWE-94 code injection issue affecting Wazuh v3.6.1-v3.13.5, v4.0.0-v4.2.7, and v4.3.0-v4.3.7. CVSS 3.1 is 8.8, with network access, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where affected Wazuh versions are deployed and authenticated users can reach the Active Response endpoint. The source bundle does not provide CPEs, deployment details, or fixed version information.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The vulnerability still has serious impact because exploitation requires only authenticated low-privilege access and no user interaction, according to the CVSS vector.

Researcher notes

The public bundle identifies the vulnerable component and version ranges but lacks CPEs, fixed versions, and detailed patch notes. Avoid assuming exploit availability or exact remediation beyond Wazuh’s PR and vendor guidance.

Mitigation direction

  • Identify Wazuh deployments and compare versions against the listed affected ranges.
  • Check Wazuh vendor guidance and PR 14801 for fixed-version details.
  • Upgrade or remediate only according to confirmed Wazuh guidance.
  • Restrict Wazuh management access to trusted users and networks.
  • Review low-privilege Wazuh accounts for necessity and unusual activity.

Validation and detection

  • Confirm whether any Wazuh instance runs an affected version range.
  • Verify who can authenticate to Wazuh management or API functions.
  • Review Active Response-related logs for unexpected authenticated activity.
  • Confirm remediation status against Wazuh’s published fix guidance.
  • Track whether CVE-2022-40497 later appears in KEV or vendor advisories.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-40497 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-40497Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.