CVE-2023-0745
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 · uneditedThe High Availability functionality of Yugabyte Anywhere can be abused to write arbitrary files through the backup upload endpoint by using path traversal characters. This vulnerability is associated with program files PlatformReplicationManager.Java. This issue affects YugabyteDB Anywhere: from 2.0.0.0 through 2.13.0.0
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 · high confidenceA path traversal vulnerability in the High Availability backup upload functionality of YugabyteDB Anywhere allows authenticated attackers to write arbitrary files to the filesystem by manipulating file paths with '..' sequences in the upload endpoint, specifically within PlatformReplicationManager.Java.
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>= 2.0, <= 2.13CVSS 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 YugabyteDB Anywhere versionCheck the installed version of YugabyteDB Anywhere. This can typically be found in the platform UI under Admin > Settings > About, or via the API endpoint /api/v1/version, or by inspecting the installation directory for version manifests.Affected if The installed version is between 2.0 and 2.13 inclusive.
-
Verify High Availability feature is configuredNavigate to the High Availability section in YugabyteDB Anywhere platform (usually under Admin > High Availability). Check if HA replication is enabled or if any HA clusters are configured.Affected if HA is enabled and backups can be uploaded to this instance.
-
Check PlatformReplicationManager exposureInspect network access controls or API gateway configurations to determine if the upload endpoint handled by PlatformReplicationManager is exposed. This endpoint typically accepts backup file uploads via the platform web interface or API.Affected if The platform upload functionality is accessible to authenticated users (non-admin or admin).
A user is affected if they are running YugabyteDB Anywhere version 2.0 through 2.13 and have the High Availability backup upload feature accessible to authenticated attackers.
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.
dbcve · scopedUpgrade YugabyteDB Anywhere to version 2.14.0.0 or later. Alternatively, implement strict input validation and path sanitization on the backup upload endpoint to reject path traversal characters before deploying the vendor patch.
Upgrade to version 2.14.0.0 or later (latest stable release)
- 1. Back up all current YugabyteDB Anywhere data and configuration
- 2. Plan maintenance window for upgrade procedure
- 3. Upgrade YugabyteDB Anywhere from version 2.13.0.0 or lower to a version beyond 2.13.0.0 (preferably the latest stable release)
- 4. After upgrade, verify the High Availability functionality works correctly
- 5. Test that the backup upload endpoint properly sanitizes path traversal attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0745 — 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-2023-0745 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