CVE-2022-43549
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper authentication in Veeam Backup for Google Cloud v1.0 and v3.0 allows attackers to bypass authentication mechanisms.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper authentication vulnerability in Veeam Backup for Google Cloud versions 1.0 and 3.0 allows unauthenticated attackers to bypass authentication mechanisms, potentially granting full access to the backup infrastructure and sensitive data stored within.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0= 3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Veeam Backup for Google Cloud versionLog into the Veeam Backup for Google Cloud web interface and navigate to the About or License section to view the product version. Alternatively, check the installed software list on the server where the product is deployed.Affected if The version displayed is exactly 1.0 or exactly 3.0 (these are the affected versions per the CVE).
-
Confirm product is internet-facingReview network firewall rules, load balancer configurations, or reverse proxy settings to determine if the Veeam Backup for Google Cloud web interface (typically on ports 443 or 8443) is exposed to untrusted networks or the public internet.Affected if The management interface is accessible from untrusted networks without VPN or IP allowlisting in place.
-
Test unauthenticated access to web interfaceAttempt to access the Veeam Backup for Google Cloud login page from an untrusted network or incognito browser session without providing credentials. Observe whether the interface loads or returns an authentication challenge.Affected if The web interface loads or returns any response other than an HTTP 401/403 authentication error without valid credentials being provided.
-
Review authentication configurationIn the Veeam Backup for Google Cloud console, navigate to Users and Roles or Authentication settings to verify that local authentication is properly enforced and that there are no misconfigured service accounts permitting anonymous access.Affected if Authentication is disabled, set to None, or allows anonymous/guest access to the backup management functions.
You are affected if your Veeam Backup for Google Cloud version is exactly 1.0 or exactly 3.0 and the management interface is accessible from untrusted networks without proper authentication enforcement.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patches or upgrade to a patched version of Veeam Backup for Google Cloud; verify authentication controls are functioning correctly post-patch.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43549 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43549 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data