CVE-2013-2018
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 · uneditedMultiple SQL injection vulnerabilities in BOINC allow remote attackers to execute arbitrary SQL commands 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 · moderate confidenceMultiple SQL injection vulnerabilities in the BOINC platform allow remote, unauthenticated attackers to execute arbitrary SQL commands by injecting malicious input through unspecified vectors. This critical flaw enables complete database compromise, potentially exposing sensitive user data, credentials, and allowing further system pivoting.
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 dataall versionsCVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 if BOINC software is installedCheck for BOINC installation directories or binaries. On Linux, look in common paths like /var/lib/boinc, /usr/bin/boinc, or run 'which boinc_client'. On Windows, check Program Files\BOINC folder. Use package managers or installed software listings.Affected if BOINC client software is found on the system
-
Determine installed BOINC versionRun 'boinc_client --version' or check the version metadata in the installation directory. On Linux, also check dpkg -l boinc-client or rpm -qi boinc-client if installed via packages.Affected if Any version of the University of California BOINC client is installed (all versions are affected)
-
Check if web interface or RPC service is exposedExamine BOINC configuration files (config.xml, cc_config.xml) for '<network>' settings. Look for '<httpd>' or web-related port configurations. Verify if the BOINC web manager or any web-facing component is enabled and bound to a network interface.Affected if The BOINC web interface or RPC service is enabled and accessible over the network (required for remote unauthenticated exploitation)
-
Review network exposureCheck listening ports using netstat -anp or ss -tlnp. Look for default BOINC ports (usually 31416 for RPC, or configured HTTP ports for web interface). Verify firewall rules and network ACLs controlling access to these services.Affected if BOINC services are bound to non-localhost interfaces or accessible from untrusted networks
If BOINC client software is present and its web interface or RPC service is network-accessible, the system is vulnerable to CVE-2013-2018 SQL injection attacks.
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-supplied patch or upgrade to a secure BOINC version. As an interim measure, deploy a WAF and implement strict input validation across all user-facing forms and API endpoints while working on parameterized query remediation.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2018 — 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-2018 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