CVE-2025-34523
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 network-facing input handling routines of Arcserve Unified Data Protection (UDP). This flaw is reachable without authentication and results from improper bounds checking when processing attacker-controlled input. By sending specially crafted data, a remote attacker can corrupt heap memory, potentially causing a denial of service or enabling arbitrary code execution depending on the memory layout and exploitation techniques used. This vulnerability is similar in nature to CVE-2025-34522 but affects a separate code path or component. No user interaction is required, and exploitation occurs in the context of the vulnerable process. 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 in Arcserve UDP's network-facing input handling routines allows remote, unauthenticated attackers to corrupt heap memory via specially crafted data due to improper bounds checking. This can lead to denial of service or arbitrary code execution in the context of the vulnerable process.
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.
-
Verify Arcserve UDP installationLocate Arcserve UDP installation directory (typically C:\Program Files\Arcserve\Unified Data Protection or check Windows Registry under HKLM\SOFTWARE\Arcserve\Unified Data Protection)Affected if Arcserve UDP is installed on the system
-
Determine installed versionCheck the version of the installed Arcserve UDP component. Common locations: Registry key 'Version' under HKLM\SOFTWARE\Arcserve\Unified Data Protection\Setup, or examine the executable properties of asurengine.exe, asunified.exe, or the Arcserve UDP Management service binary.Affected if Version is less than 7.0, equals 7.0, or is greater than or equal to 8.0 but less than 10.2
-
Confirm network-facing component is enabledIdentify if the Arcserve UDP network listener service (typically the 'Arcserve UDP Remote' or 'ASUDP Remote' service) is running and accepting network connections on ports 41522, 41523, or similar UDP listener ports.Affected if Network listener service is active and exposed to network traffic
-
Check for vulnerable network input handlingVerify that the UDP listener component responsible for receiving remote management or backup data is enabled. This is typically controlled via the Arcserve UDP Management console under 'Configuration' - 'Network Settings' - 'Listener Settings'.Affected if Network listener for remote management or backup operations is enabled and reachable
User is affected if Arcserve UDP is installed with a version less than 10.2 AND the network-facing listener service is enabled and accessible to remote 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 · scoped7.010.2
Upgrade to UDP version 10.2 or apply the available patch to supported versions 8.0-10.1. Versions 7.x and earlier require an upgrade to 10.2.
Arcserve UDP 10.2
- Obtain Arcserve Unified Data Protection version 10.2 from the official vendor (support.arcserve.com) or authorized distribution channels
- Review the Arcserve UDP 10.2 release notes and upgrade prerequisites documented on support.arcserve.com
- Ensure all critical business data protected by UDP is backed up before initiating the upgrade
- Stop the Arcserve UDP services on the target system prior to upgrade
- Install Arcserve UDP version 10.2 following the vendor's installation documentation
- After installation, verify that the UDP services start successfully
- Confirm the version number displays as 10.2 in the Arcserve UDP administrative console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34523 — 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-34523 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