Apply updates per vendor instructions.
Evidence dossier
CVE-2015-4068
CVE-2015-4068
gen-56ccdaf9Normalized restatement
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.
- State
- PUBLISHED
- Published
- May 29, 2015
- Updated
- Oct 21, 2025
- Evidence coverage
- 72%
2026-07-18 · v2026.06.15 · percentile 99.1%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
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.
Arcserve Unified Data Protection (UDP) Directory Traversal Vulnerability
Probability 0.636430000000; percentile 0.991250000000
Applicability
Cited product scope
[{"status": "affected", "version": "n/a"}]unknowncpe:2.3:a:arcserve:udp:*:*:*:*:*:*:*:*; end excluding 5.0supportedcpe:2.3:a:arcserve:udp:5.0:-:*:*:*:*:*:*supportedAssessments
CVSS by origin
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HAV:N/AC:L/Au:N/C:C/I:N/A:CCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.