CVE-2013-2019
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 · uneditedStack-based buffer overflow in BOINC 6.10.58 and 6.12.34 allows remote attackers to have unspecified impact via multiple file_signature elements.
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 confidenceStack-based buffer overflow in BOINC client versions 6.10.58 and 6.12.34 allows remote attackers to execute arbitrary code via multiple file_signature elements, likely during XML project file parsing. The vulnerability has a CVSS score of 9.3, indicating critical severity with potential for complete system compromise.
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= 6.10.58= 6.12.34CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/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.
-
Locate BOINC client installationOn Linux: which boinc_client or ls /usr/bin/boinc*; On Windows: check Program Files for BOINC folder or look for boinc.exe in system directoriesAffected if BOINC client executable is found on the system
-
Determine installed BOINC versionRun 'boinc_client --version' (Linux) or check boinc.exe properties (Windows). On Linux, also check dpkg -l | grep boinc or rpm -qa | grep boincAffected if Version returned is exactly 6.10.58 or exactly 6.12.34
-
Check if BOINC client is runningOn Linux: ps aux | grep boinc; On Windows: open Task Manager and look for boinc.exe or boincmgr.exeAffected if BOINC client process is active and connected to any project server
-
Verify project configuration files existOn Linux: ls ~/.boinc/ or /var/lib/boinc/ for project config XML files; On Windows: check C:\ProgramData\BOINC\ for project configuration filesAffected if Project configuration files exist, indicating BOINC has connected to project servers and performed XML parsing
The environment is affected if BOINC client version 6.10.58 or 6.12.34 is installed and the client is configured to connect to project servers, enabling the vulnerable XML project file parsing code path.
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 BOINC client to a version beyond 6.12.34 that contains the patch for this vulnerability, or apply vendor-supplied patches if available. If immediate patching is not possible, restrict network communication to trusted BOINC project servers only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2019 — 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-2019 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