CVE-2013-4575
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 · uneditedHeap-based buffer overflow in the utility program in the Linux agent in Symantec Backup Exec 2010 R3 before 2010 R3 SP3 and 2012 before SP2 allows remote attackers to cause a denial of service (agent crash) or possibly execute arbitrary code via unspecified vectors.
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 confidenceHeap-based buffer overflow vulnerability in the Linux agent utility program of Symantec Backup Exec 2010 R3 and 2012 allows remote attackers to potentially execute arbitrary code or cause denial of service via unspecified vectors.
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= 2010= 2012CVSS 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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:M/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.
-
Identify Backup Exec installation and versionOpen Backup Exec console, go to Help > About, or check Windows Registry at HKLM\SOFTWARE\Symantec\Backup Exec\Install\RegKey for version valueAffected if Version displayed is exactly 2010 or 2012
-
Confirm the Linux agent component is presentCheck Program Files\Symantec\Backup Exec\ directory for RAWSx64 or RAWSx86 folders (Linux agent remote agent), or open Backup Exec console and navigate to Storage > click on the backup device to see installed agentsAffected if Linux agent (RAWS) is installed or listed as an available agent
-
Verify Linux agent service or executable existsCheck for presence of beremote.exe or related Linux agent binaries in the Backup Exec installation directory, or view installed Agent instances in Backup Exec Administration consoleAffected if Linux agent executable/service is present on the system
-
Cross-reference version against affected releaseIf version is 2010, confirm it is R3 (2010 R3). If version is 2012, confirm it is version 2012. The vulnerability specifically affects these release versions with the Linux agent componentAffected if Running Backup Exec 2010 R3 or Backup Exec 2012 with the Linux agent installed
System is affected if Symantec Backup Exec version 2010 R3 or 2012 is installed AND the Linux agent component (RAWS) is present on the system.
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 dataUpgrade Symantec Backup Exec 2010 R3 to at least SP3 and 2012 to at least SP2 to patch the vulnerability in the Linux agent.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4575 — 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-2013-4575 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