CVE-2007-1785
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 RPC service in mediasvr.exe in CA BrightStor ARCserve Backup 11.5 SP2 build 4237 allows remote attackers to execute arbitrary code via crafted xdr_handle_t data in RPC packets, which is used in calculating an address for a function call, as demonstrated using the 191 (0xbf) RPC 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 · high confidenceThe RPC service in mediasvr.exe in CA BrightStor ARCserve Backup 11.5 SP2 contains a memory corruption vulnerability where crafted xdr_handle_t data in RPC packets is used to calculate a function call address, allowing remote attackers to execute arbitrary code. The vulnerability is triggered via RPC request 191 (0xbf).
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= 9.01= 11.1= 11.5= 11CVSS 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
- High
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/Au:S/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.
-
Confirm BrightStor ARCserve Backup is installedCheck for the presence of the CA BrightStor ARCserve Backup installation directory (typically under C:\Program Files\CA\BrightStor ARCserve Backup\) or look for mediasvr.exe process in Task ManagerAffected if The product is installed on the system
-
Identify the installed versionRight-click on mediasvr.exe in the installation directory, select Properties, and view the Version tab. Alternatively, check the main ARCserve installation for its version numberAffected if The version matches 9.01, 11.1, or 11.5 (Broadcom) or version 11 (CA)
-
Verify mediasvr.exe RPC service is runningOpen Task Manager or run 'tasklist /FI "IMAGENAME eq mediasvr.exe"' in command prompt to check if the mediasvr.exe process is activeAffected if The mediasvr.exe process is currently running
-
Check network exposure of the RPC serviceRun 'netstat -an' and look for listening ports associated with mediasvr.exe (the RPC service typically listens on dynamic ports). Use 'netsh firewall show portopening' to check if firewall exceptions existAffected if The RPC service port is open and accessible from network hosts
You are affected if BrightStor ARCserve Backup version 9.01, 11.1, or 11.5 is installed AND the mediasvr.exe RPC service is running and exposed on the network.
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 the vendor patch for CA BrightStor ARCserve Backup 11.5 SP2; if no patch is available due to product EOL, upgrade to a supported version or restrict network access to the RPC service via firewall.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1785 — 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-1785 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