dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022.
UdpApplication · Arcserve

CVE-2015-4068

CRITICAL · 9.1 CVSS v3.1 Published 2015-05-29
Fix available
A fix is available. Upgrade to 5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS 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
Directory traversal vulnerability in Arcserve UDP before 5.0 Update 4 allows remote attackers to obtain sensitive information or cause a denial of service via a crafted file path to the (1) reportFileServlet or (2) exportServlet servlet.

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

Directory traversal vulnerability in Arcserve UDP before version 5.0 Update 4 allows remote unauthenticated attackers to access arbitrary files on the filesystem by using '..' path traversal sequences in requests to the reportFileServlet or exportServlet servlets, potentially exposing sensitive configuration or system files.

MitigationUpdate Arcserve UDP to version 5.0 Update 4 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to the affected servlet endpoints and implement web application firewall rules to block path traversal patterns.

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
UdpApplication
Affected:< 5.0= 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify installed Arcserve UDP version
    Locate the Arcserve UDP installation and check its version information through the product's built-in version display or system information component
    Affected if The installed version is any version prior to 5.0, or exactly version 5.0 (prior to Update 4)
  2. Confirm web server component is running
    Verify that the Arcserve UDP web server or management console service is active and listening on its configured port
    Affected if The web interface is exposed and accessible to network users or attackers
  3. Test access to reportFileServlet
    Send an HTTP request to the reportFileServlet endpoint using a manipulated path parameter (e.g., ../../) to attempt directory traversal
    Affected if The servlet responds and allows path traversal outside the web root directory
  4. Test access to exportServlet
    Send an HTTP request to the exportServlet endpoint using a manipulated path parameter to attempt directory traversal
    Affected if The servlet responds and allows path traversal outside the web root directory

A system is affected if Arcserve UDP version is less than 5.0 or exactly 5.0, and the web-based servlets (reportFileServlet or exportServlet) are exposed and accessible to unauthorized users.

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.

dbcve · scoped
Upgrade available Upgrade to 5.0 or later
Fixed in 5.0
Interim mitigation

Update Arcserve UDP to version 5.0 Update 4 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to the affected servlet endpoints and implement web application firewall rules to block path traversal patterns.

Recommended fix High confidence

Arcserve UDP 5.0 Update 4 or later

  1. Verify current Arcserve UDP version by accessing the administration console or checking the installed software
  2. Download Arcserve UDP 5.0 Update 4 or later from the official ArcServe website or authorized download portal
  3. Review the upgrade guide and release notes for Arcserve UDP 5.0 Update 4 for any prerequisites
  4. Create a full backup of the Arcserve UDP configuration and data before proceeding with the upgrade
  5. Stop all Arcserve UDP services prior to installation
  6. Run the installer for Arcserve UDP 5.0 Update 4 or later
  7. Follow the on-screen installation wizard prompts to complete the upgrade
  8. Restart Arcserve UDP services after installation completes
Caveat Review Arcserve UDP 5.0 Update 4 release notes for any configuration or feature changes that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Udp Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,260
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4068 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-4068 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