CVE-2010-3984
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 · uneditedBuffer overflow in mng_core_com.dll in CA XOsoft Replication r12.0 SP1 and r12.5 SP2 rollup, CA XOsoft High Availability r12.0 SP1 and r12.5 SP2 rollup, CA XOsoft Content Distribution r12.0 SP1 and r12.5 SP2 rollup, and CA ARCserve Replication and High Availability (RHA) r15.0 SP1 allows remote attackers to execute arbitrary code via a crafted create_session_bab operation in a SOAP request to xosoapapi.asmx.
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 confidenceBuffer overflow vulnerability in mng_core_com.dll in CA XOsoft/ARCserve products allows remote attackers to execute arbitrary code via a crafted create_session_bab operation in a SOAP request to the xosoapapi.asmx endpoint.
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= r15.0= r12.0= r12.5= r12.0= r12.5= r12.0= r12.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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Identify installed CA XOsoft/ARCserve productsCheck installed programs in Control Panel or registry for CA XOsoft Replication, CA XOsoft High Availability, CA XOsoft Content Distribution, or CA Arcserve Replication And High AvailabilityAffected if Any of these products are installed at versions r12.0, r12.5, or r15.0
-
Verify xosoft SOAP API endpoint is exposedCheck if xosoapapi.asmx is accessible on the server - attempt to access http(s)://<server>/xosoapapi.asmx from a browser or curl commandAffected if The endpoint returns a SOAP service description page (indicating the web service is running and exposed)
-
Locate and identify mng_core_com.dll versionSearch for mng_core_com.dll in the product installation directory - typical paths may include C:\Program Files\CA\XOsoft\ or C:\Program Files\CA\ARCserve\ - right-click the file, select Properties, and check the Version tabAffected if The file exists and corresponds to an unpatched product version (compare the file version against the affected version ranges)
-
Confirm SOAP create_session_bab operation is availableSend a test SOAP request to xosoapapi.asmx with a create_session_bab operation - this typically requires network access to the endpointAffected if The service accepts and processes this operation without error, indicating the vulnerable code path is reachable
The system is affected if any CA XOsoft/ARCserve product at version r12.0, r12.5, or r15.0 is installed with the xosoapapi.asmx web service exposed and the vulnerable mng_core_com.dll is present at an unpatched version.
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 from CA for the affected products (XOsoft Replication/High Availability/Content Distribution r12.0 SP1/r12.5 SP2 and ARCserve RHA r15.0 SP1). Until patched, restrict network access to xosoapapi.asmx or implement WAF rules to block malformed SOAP requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3984 — 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-2010-3984 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