dbcve.org
Boinc ServerApplication · Universityofcalifornia

CVE-2018-1000875

CRITICAL · 9.8 CVSS v3.1 Published 2018-12-20
Fix available
A fix is available. Upgrade to 1.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Berkeley Open Infrastructure for Network Computing BOINC Server and Website Code version 0.9-1.0.2 contains a CWE-302: Authentication Bypass by Assumed-Immutable Data vulnerability in Website Terms of Service Acceptance Page that can result in Access to any user account. This attack appear to be exploitable via Specially crafted URL. This vulnerability appears to have been fixed in 1.0.3.

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 confidence

BOINC Server and Website Code versions 0.9-1.0.2 contain an authentication bypass vulnerability (CWE-302) in the Terms of Service acceptance page. The vulnerability allows attackers to access any user account via a specially crafted URL that exploits the assumption of immutable data in the authentication mechanism.

MitigationUpgrade to BOINC Server version 1.0.3 or later to remediate this vulnerability. Given the CVSS 9.8 critical rating, this upgrade should be prioritized and performed as soon as possible.

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
Boinc ServerApplication
Affected:>= 1.0.0, < 1.0.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed BOINC Server version
    Locate the BOINC Server installation and retrieve its version number from the software, configuration files, or package manager. Common locations include /var/www/boinc, /opt/boinc, or within the web server document root. Check version files, about pages, or use command-line tools if available.
    Affected if The installed version is 1.0.0, 1.0.1, or 1.0.2 (any version >= 1.0.0 but < 1.0.3)
  2. Confirm the Terms of Service acceptance functionality exists
    Search the BOINC Server web application for the Terms of Service (ToS) acceptance page or endpoint. Look for files or routes related to 'tos', 'terms', 'accept', or 'legal' within the server codebase.
    Affected if The ToS acceptance feature is present in the installation and version is < 1.0.3
  3. Verify authentication mechanism uses ToS for user validation
    Examine the authentication code in the BOINC Server to determine if the Terms of Service acceptance status is used as part of the login or session validation logic. Check for conditions that grant access based on ToS acceptance state.
    Affected if The authentication mechanism relies on ToS acceptance status and version is vulnerable
  4. Check web server configuration for BOINC Server
    Identify the web server (Apache, Nginx, etc.) serving the BOINC Server application and confirm it is running the affected version of the software by inspecting server logs, installed packages, or application metadata.
    Affected if The web server runs BOINC Server versions 1.0.0 through 1.0.2

A defender is affected if their BOINC Server installation is version 1.0.0, 1.0.1, or 1.0.2 and includes the Terms of Service acceptance feature that is exploited by the authentication bypass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.3 or later
Fixed in 1.0.3
Interim mitigation

Upgrade to BOINC Server version 1.0.3 or later to remediate this vulnerability. Given the CVSS 9.8 critical rating, this upgrade should be prioritized and performed as soon as possible.

Recommended fix High confidence

1.0.3

  1. Identify current Boinc Server version by checking installation or version file
  2. Obtain Boinc Server version 1.0.3 from the official GitHub repository or release channel
  3. Review upgrade documentation specific to your deployment method
  4. Perform a backup of the existing installation and database
  5. Stop Boinc Server services
  6. Install version 1.0.3 following standard upgrade procedures
  7. Verify the Terms of Service acceptance mechanism no longer contains the authentication bypass
  8. Restart Boinc Server services

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Boinc Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000875 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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