CVE-2025-34522
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 · uneditedA heap-based buffer overflow vulnerability exists in the input parsing logic of Arcserve Unified Data Protection (UDP). This flaw can be triggered without authentication by sending specially crafted input to the target system. Improper bounds checking allows an attacker to overwrite heap memory, potentially leading to application crashes or remote code execution. Exploitation occurs in the context of the affected process and does not require user interaction. The vulnerability poses a high risk due to its pre-authentication nature and potential for full compromise. This vulnerability affects all UDP versions prior to 10.2. UDP 10.2 includes the necessary patches and requires no action. Versions 8.0 through 10.1 are supported and require either patch application or upgrade to 10.2. Versions 7.x and earlier are unsupported or out of maintenance and must be upgraded to 10.2 to remediate the issue.
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 heap-based buffer overflow exists in Arcserve UDP's input parsing logic due to improper bounds checking during input processing. This allows unauthenticated remote attackers to overwrite heap memory and potentially achieve remote code execution without any user interaction.
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< 7.0>= 8.0, < 10.2= 7.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 Arcserve UDP installation path and versionLocate the Arcserve UDP installation directory (commonly C:\Program Files\Arcserve\Arcserve UDP or C:\Program Files (x86)\Arcserve\Arcserve UDP). Within the installation folder, locate the main executable (often UDP.exe, asygui.exe, or similar) and right-click to view Properties, then check the Details tab for the Product Version. Alternatively, open Windows Control Panel > Programs and Features, find Arcserve UDP in the list, and note the installed version shown there.Affected if The installed version is any version prior to 10.2, including all 7.x versions and versions 8.0 through 10.1.
-
Verify the Arcserve UDP service is runningOpen Windows Services (services.msc) and locate the Arcserve UDP service (commonly named 'Arcserve UDP' or 'Arcserve Unified Data Protection'). Check if the Status column shows 'Running'. Alternatively, open Task Manager, go to the Services tab, and look for the Arcserve service.Affected if The service is running and the version is vulnerable (prior to 10.2).
-
Confirm network listener is enabled on the Arcserve UDP management portOpen Command Prompt and run 'netstat -an | findstr LISTENING' to list all listening ports. Look for ports commonly used by Arcserve UDP (such as 8014, 8080, 8443, or the configured management port). Verify the Arcserve management interface is bound to these ports by checking the Arcserve UDP configuration console under Network Settings or Server Settings.Affected if The management interface port is listening and the installed version is vulnerable.
-
Check if remote access policies permit unauthenticated connectionsOpen the Arcserve UDP console and navigate to Server Settings or Administration > Security Settings. Verify whether the configuration allows unauthenticated or anonymous remote connections to the management interface. Check for any settings labeled 'Allow remote administration' or 'Enable remote console access' that may be enabled without authentication requirements.Affected if Remote unauthenticated access is enabled and the version is vulnerable.
If Arcserve UDP is installed and running with a version lower than 10.2, and the management interface is exposed with unauthenticated access permitted, the environment is affected by this vulnerability.
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 · scoped7.010.2
Upgrade to Arcserve UDP version 10.2 to obtain the patched version, or apply the available patch to versions 8.0-10.1. Versions 7.x and earlier are unsupported and require upgrade to 10.2.
10.2
- Identify the current Arcserve Unified Data Protection (UDP) version installed in the environment
- If running version 7.x or earlier: Plan migration to version 10.2 as these versions are unsupported
- If running version 8.0 through 10.1: Apply the available patch from support.arcserve.com OR plan upgrade to version 10.2
- Download Arcserve UDP version 10.2 from the official vendor portal or support site
- Before upgrading, back up all critical data and configuration settings
- Execute the upgrade process following the vendor's official documentation
- Verify the upgrade was successful and the new version is running
- Confirm version 10.2 is active to ensure the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34522 — 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-2025-34522 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