CVE-2007-1447
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 · uneditedThe Tape Engine in CA (formerly Computer Associates) BrightStor ARCserve Backup 11.5 and earlier allows remote attackers to cause a denial of service and possibly execute arbitrary code via certain RPC procedure arguments, which result in memory corruption, a different vulnerability than CVE-2006-6076.
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 confidenceThe Tape Engine component in CA BrightStor ARCserve Backup 11.5 and earlier contains a memory corruption vulnerability triggered by specially crafted RPC procedure arguments, allowing remote attackers to cause denial of service or potentially execute arbitrary code.
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<= 11.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify BrightStor ARCserve Backup is installedCheck for the presence of CA BrightStor ARCserve Backup installation directories (typically C:\Program Files\CA\BrightStor ARCserve Backup\) or review Add/Remove Programs for a BrightStor ARCserve Backup entryAffected if BrightStor ARCserve Backup is present on the system
-
Determine the installed versionLocate the version information in the registry at HKLM\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\CurrentVersion\ProductVersion, or check the version property of the caspbkup.exe file in the installation directoryAffected if The installed version is 11.5 or earlier (version number less than or equal to 11.5)
-
Verify Tape Engine service is runningOpen Windows Services console and look for 'CA BrightStor ARCserve Backup Tape Engine' service, or check for the tapeeng.exe process running in Task ManagerAffected if The Tape Engine service is running as a running process or active Windows service
-
Check RPC listener network exposureRun 'netstat -an' and look for the Tape Engine RPC port (commonly UDP port 605 or as configured) in a listening state. Verify whether it is bound to 0.0.0.0 (all interfaces) rather than only 127.0.0.1 (localhost)Affected if The Tape Engine RPC service is listening on a network-accessible port (bound to 0.0.0.0 or external IP rather than localhost only)
The environment is affected if BrightStor ARCserve Backup version 11.5 or earlier is installed with the Tape Engine RPC service running and exposed to network access.
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.
From vendor dataApply vendor patches or upgrade to a supported version of BrightStor ARCserve Backup. If patching is not immediately possible, restrict network access to the Tape Engine RPC service and monitor for exploitation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1447 — 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-2007-1447 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