Threats / Veeam / CVE-2023-27532
CVE-2023-27532
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Veeam Backup & Replication vulnerability
Veeam Backup & Replication Cloud Connect lacks authentication for critical functions, allowing unauthenticated network-adjacent attackers to extract encrypted credentials and compromise backup infrastructure.
Verdict
Today item, not a backlog item.
Missing authentication in a critical backup component enables credential theft and lateral movement within backup infrastructure. Active exploitation and ransomware campaigns demonstrate immediate operational risk to organizations relying on Veeam for data protection.
CISA KEV Yes · 2023-08-223Ransomware use Flagged3EPSS 0.7761 (verify live)4Exploit Weaponized · public PoC5
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
58 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-08-22), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.7761 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Veeam, Backup & Replication. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-306 Missing Authentication — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain network access to the backup infrastructure perimeter and exploit the unauthenticated Cloud Connect component to query the configuration database.
Business
Attackers establish initial access to the backup environment without credentials, bypassing primary security controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract encrypted credentials stored in the database and decrypt them to obtain valid authentication material for backup infrastructure hosts.
Business
Credential compromise exposes administrative access to backup systems, enabling lateral movement and persistence.
3
Lateral reach — past segmentation narrative 3
Attacker
I use obtained credentials to access backup infrastructure hosts and enumerate backup repositories containing production data.
Business
Attackers gain direct access to backup data, circumventing primary production defenses and enabling data exfiltration or destruction.
4
Data at risk — exfiltration narrative 4
Attacker
I encrypt or delete backup repositories to render recovery impossible, then demand ransom while production systems remain compromised.
Business
Organization loses backup recovery capability during active incident, forcing choice between ransom payment or permanent data loss.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05