CVE-2012-1662
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 · uneditedCA ARCserve Backup r12.0 through SP2, r12.5 before SP2, r15 through SP1, and r16 before SP1 on Windows allows remote attackers to cause a denial of service (service shutdown) via a crafted network request.
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 · moderate confidenceCA ARCserve Backup versions r12.0 through r12.5, r15 through r15 SP1, and r16 before SP1 on Windows contain a vulnerability in the backup service that allows remote attackers to cause a denial of service via crafted network requests, resulting in service shutdown.
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= r16.0CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 ARCserve Backup is installedCheck for ARCserve Backup installation by looking in Program Files for 'CA' or 'ARCserve' folders, or use Add/Remove Programs to list installed softwareAffected if CA ARCserve Backup appears in installed programs
-
Determine installed versionLocate the version information in the ARCserve installation (typically in About or in the installation directory), or run: cacmd -version or check registry under HKLM\Software\ComputerAssociates\ARCserve\Backup\Base\ProductAffected if Version is r12.0 through r12.5, r15.0 through r15 SP1, or r16.0 (before SP1)
-
Confirm backup service is runningOpen Services console (services.msc) and look for 'ARCserve Backup' or 'CAServer' service, or run: net start | findstr "ARCserve"Affected if The ARCserve Backup service is currently running and accepting network requests
-
Check network exposure of service portsRun 'netstat -an | findstr LISTENING' to identify ports ARCserve is listening on (common ports: 41524, 41523, 3077, 3078), or review firewall rules for inbound rules allowing traffic to these portsAffected if ARCserve service ports are accessible from untrusted networks or the internet
You are affected if CA ARCserve Backup is installed and running a vulnerable version (r12.0-r12.5, r15-r15 SP1, or r16.0 before SP1) with exposed network ports.
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 for the specific version (r12.5 SP2, r15 SP2, r16 SP1 or later) or upgrade to a patched release; if immediate patching is not possible, implement network segmentation and firewall rules to restrict unauthorized network access to the ARCserve Backup service ports.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1662 — 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-2012-1662 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