# CVE-2022-43549: Auth bypass in Veeam Backup for Google Cloud

> Attackers can bypass authentication mechanisms in Veeam Backup for Google Cloud, potentially gaining unauthorized access to backup services.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-xqhh-f594-fg34

## What is CVE-2022-43549?

CVE-2022-43549 is a critical authentication bypass vulnerability in Veeam Backup for Google Cloud, published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper authentication in Veeam Backup for Google Cloud v1.0 and v3.0 allows attackers to bypass authentication mechanisms.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-43549?

It affects 1 product.


Products: Veeam Veeam Backup for Google Cloud.

## How do I fix CVE-2022-43549?

No fix has been published for CVE-2022-43549 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-43549 being exploited?

There is no known exploitation of CVE-2022-43549 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43549 and fix it if it is affected.

What it is: CVE-2022-43549 is a critical authentication bypass vulnerability in Veeam Backup for Google Cloud, published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43549 in the wild and no public exploit code.

Affected product: Veeam Backup for Google Cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-43549/ (Markdown: https://insights.sbomify.com/CVE-2022-43549/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-43549
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-43549
- OSV: https://osv.dev/vulnerability/CVE-2022-43549

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-43549/
Summaries are generated and may contain mistakes; the official description above is the record.