Arcserve Unified Data ProtectionApplication · Arcserve

CVE-2015-4069

HIGH · 7.8 CVSS v2.0 Published 2015-05-29
Fix available
A fix is available. Upgrade to after 5.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The EdgeServiceImpl web service in Arcserve UDP before 5.0 Update 4 allows remote attackers to obtain sensitive credentials via a crafted SOAP request to the (1) getBackupPolicy or (2) getBackupPolicies method.

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 confidence

The EdgeServiceImpl SOAP web service in Arcserve UDP versions prior to 5.0 Update 4 contains insecure methods (getBackupPolicy and getBackupPolicies) that return sensitive credentials without requiring authentication, allowing unauthenticated remote attackers to retrieve backup policy credentials via crafted SOAP requests.

MitigationUpgrade Arcserve UDP to version 5.0 Update 4 or later which addresses the improper authorization in the EdgeServiceImpl web service. If immediate patching is not possible, consider network segmentation to restrict access to the web service port.

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
Arcserve Unified Data ProtectionApplication
Affected:<= 5.0

CVSS 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
Authentication
None
Confidentiality
Complete
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:C/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Arcserve UDP installation and version
    Check installed programs or services list for 'Arcserve Unified Data Protection' or 'Arcserve UDP' and note the version number. On Windows, this can be done via Control Panel > Programs and Features, or by checking the Arcserve service information.
    Affected if The installed version is 5.0 or any version prior to 5.0 Update 4.
  2. Locate the EdgeServiceImpl web service endpoint
    Review Arcserve UDP documentation or configuration files to identify the SOAP web service endpoint URL. The EdgeServiceImpl service is typically exposed via HTTP on a configured port (commonly 8080 or 8085).
    Affected if The EdgeServiceImpl SOAP endpoint is accessible over the network and responds to requests.
  3. Verify if the service allows unauthenticated access
    Send a crafted SOAP request to the EdgeServiceImpl endpoint invoking the getBackupPolicy or getBackupPolicies method without providing any authentication credentials. Check if the response contains backup policy names, usernames, passwords, or other sensitive credential data.
    Affected if The web service returns sensitive backup policy credentials (such as usernames, passwords, or domain credentials) without requiring any authentication.
  4. Confirm the version is vulnerable based on Update level
    If the version displays as 5.0, determine whether Update 4 has been applied by checking the exact build number or Update package level in the Arcserve UDP management console or installed updates list.
    Affected if The version is 5.0 without Update 4 applied, or the build number indicates an update level prior to Update 4.

If Arcserve UDP version 5.0 or earlier is installed AND the EdgeServiceImpl SOAP web service returns credential data without authentication, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.0
Interim mitigation

Upgrade Arcserve UDP to version 5.0 Update 4 or later which addresses the improper authorization in the EdgeServiceImpl web service. If immediate patching is not possible, consider network segmentation to restrict access to the web service port.

Fix this in Arcserve Unified Data Protection Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4069 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-4069 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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