LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40711: A deserialization of untrusted data vulnerability with a malicious payload can allow an unauthenticated rem...

A deserialization of untrusted data vulnerability with a malicious payload can allow an unauthenticated remote code execution (RCE).

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-40711 is a critical Veeam deserialization flaw that can let an unauthenticated remote attacker run code. Because CISA lists it in KEV, organizations should treat exposed or unpatched Veeam backup systems as urgent risk.

Executive priority

Treat this as urgent. It affects backup infrastructure, has unauthenticated remote code execution characteristics, and is listed by CISA as known exploited. Remediation should be tracked at executive risk level until verified closed.

Technical view

The CVE describes CWE-502 deserialization of untrusted data leading to unauthenticated RCE, with CVSS 9.8 network attack characteristics. The bundle identifies Veeam Backup and Recovery 12.1.2 as affected and references Veeam KB4649 and watchTowr research.

Likely exposure

Exposure is most concerning where Veeam Backup and Recovery 12.1.2 is reachable from untrusted networks or not aligned with Veeam KB4649 guidance. Backup infrastructure often has high privileges, making compromise operationally severe.

Exploitation context

Active exploitation is supported by CISA KEV listing for CVE-2024-40711. Public research from watchTowr is cited, but this assessment does not provide exploit mechanics or assume exploitation beyond the KEV evidence.

Researcher notes

Evidence confirms CWE-502, unauthenticated RCE impact, CVSS 9.8, affected Veeam 12.1.2, and KEV status. The provided bundle does not include detailed patch version text, so remediation should be verified directly against Veeam KB4649.

Mitigation direction

  • Identify Veeam Backup and Recovery 12.1.2 deployments.
  • Follow Veeam KB4649 for vendor-approved updates or mitigations.
  • Restrict Veeam service exposure to trusted administrative networks.
  • Prioritize remediation for internet-facing or cross-network reachable backup servers.
  • Monitor CISA KEV due dates and internal remediation ownership.

Validation and detection

  • Inventory Veeam product versions against the affected 12.1.2 entry.
  • Confirm whether affected services are reachable from untrusted networks.
  • Verify remediation status against Veeam KB4649, not informal guidance.
  • Review security logs for suspicious access to Veeam backup infrastructure.
  • Document compensating controls if immediate vendor remediation is delayed.
Prepared
Reviewed
Confidence
high
Sources
5

Michael Williams reviewed this cited source version on .

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-502: 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-2024-40711 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
Critical
CVSS
9.8 (3.0)
Known Exploited
Yes
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/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
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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
9.8CVSS 3.0CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

9.8Critical
CVSS 3.0 vector shape for CVE-2024-40711Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VeeamBackup and Recovery12.1.2unaffected
Weakness

CWE details

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

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.