dbcve.org
Brightstor Arcserve BackupApplication · Broadcom

CVE-2006-6076

HIGH · 10.0 CVSS v2.0 Published 2006-11-24
Fix available
A fix is available. Upgrade to after 11.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Buffer overflow in the Tape Engine (tapeeng.exe) in CA (formerly Computer Associates) BrightStor ARCserve Backup 11.5 and earlier allows remote attackers to execute arbitrary code via certain RPC requests to TCP port 6502.

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

A buffer overflow vulnerability exists in the Tape Engine (tapeeng.exe) component of CA BrightStor ARCserve Backup 11.5 and earlier. The vulnerability is exploitable through specially crafted RPC requests sent to TCP port 6502, allowing remote attackers to execute arbitrary code with the privileges of the affected service.

MitigationUpgrade to a patched version of CA BrightStor ARCserve Backup. If immediate patching is not feasible, block or restrict access to TCP port 6502 at the network perimeter until the upgrade can be completed.

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
Brightstor Arcserve BackupApplication
Affected:<= 11.5= 11.1= 11.5
Brightstor Arcserve BackupApplication
Affected:= 11= 11.1
Brightstor Arcserve Backup AgentApplication
Affected:= 11.0= 11.1

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
Complete
Availability
Complete

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

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. Verify BrightStor ARCserve Backup installation and version
    Check installed programs in Control Panel > Programs and Features, or query the Windows Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode} for the DisplayVersion value, or run 'tapeeng.exe -version' if available
    Affected if The installed version is 11.5, 11.1, 11, or any version earlier than or equal to 11.5
  2. Confirm Tape Engine component is present
    Locate the file tapeeng.exe on the system. Common paths include C:\Program Files\CA\BrightStor ARCserve Backup\ or C:\Program Files\CA\ARCserve Backup\. Use 'tasklist /FI "IMAGENAME eq tapeeng.exe"' to check if the process is running, or 'where /R C:\ tapeeng.exe' to find the executable
    Affected if tapeeng.exe exists on the system and is running as a service
  3. Check if TCP port 6502 is listening
    Run 'netstat -an | findstr :6502' or use a port scanner against localhost on TCP port 6502. Also verify in Windows Firewall or registry that the port is open
    Affected if TCP port 6502 is in LISTENING state or open in the firewall, indicating the RPC service is active for the Tape Engine
  4. Verify RPC service configuration for Tape Engine
    Check Windows Services console (services.msc) for the 'CA BrightStor ARCserve Backup Tape Engine' service, or check registry under HKLM\SYSTEM\CurrentControlSet\Services\CASABTPE for Start type. The RPC listener for port 6502 is enabled by default when the service runs
    Affected if The Tape Engine service is set to Automatic or Manual start and is currently running
  5. Compare installed version to affected ranges
    Document the exact version number from step 1 and compare against the affected versions: 11.5, 11.1, 11, or any version <= 11.5. Contact Broadcom/CA support if version cannot be determined
    Affected if The installed version falls within <= 11.5, or specifically matches 11, 11.1, or 11.5

A system is affected if CA BrightStor ARCserve Backup version 11.5 or earlier is installed, the Tape Engine (tapeeng.exe) service is running, and TCP port 6502 is open and listening for RPC requests.

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 11.5
Interim mitigation

Upgrade to a patched version of CA BrightStor ARCserve Backup. If immediate patching is not feasible, block or restrict access to TCP port 6502 at the network perimeter until the upgrade can be completed.

Fix this in Brightstor Arcserve Backup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-6076 — 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-2006-6076 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