dbcve.org
Intense Pc FirmwareOperating system · Compulab

CVE-2017-8083

MEDIUM · 6.7 CVSS v3.0 Published 2017-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
CompuLab Intense PC and MintBox 2 devices with BIOS before 2017-05-21 do not use the CloseMnf protection mechanism for write protection of flash memory regions, which allows local users to install a firmware rootkit by leveraging administrative privileges.

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

The CompuLab Intense PC and MintBox 2 devices running BIOS versions prior to 2017-05-21 lack the CloseMnf protection mechanism for write-protecting flash memory regions. This allows a local user with administrative privileges to write to the flash memory and install a firmware rootkit.

MitigationUpdate the BIOS to version 2017-05-21 or later which implements the CloseMnf protection mechanism for flash memory write protection.

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
Intense Pc FirmwareOperating system
Affected:<= cr_2.2.0.400.2
Mintbox 2 FirmwareOperating system
Affected:<= cr_2.2.0.400.2

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:H/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 the device model
    Locate the device label on the chassis or run 'dmidecode -s system-product-name' to confirm the system is a CompuLab Intense PC or MintBox 2
    Affected if The model is Intense PC or MintBox 2
  2. Check the BIOS/firmware version
    Run 'dmidecode -s bios-version' or access the BIOS setup screen during boot to view the firmware version
    Affected if The firmware version is at or below cr_2.2.0.400.2
  3. Verify the BIOS release date
    Run 'dmidecode -s bios-release-date' to determine if the BIOS was released prior to 2017-05-21
    Affected if The BIOS release date is before 2017-05-21
  4. Confirm flash write protection status
    Inspect the BIOS settings under Security or Advanced menu for any flash memory write protection or CloseMnf setting, if accessible
    Affected if No flash write protection or CloseMnf mechanism is enabled or available in the BIOS settings

A user is affected if they own an Intense PC or MintBox 2 with firmware version cr_2.2.0.400.2 or earlier, or with a BIOS dated before 2017-05-21 that lacks the CloseMnf flash write protection mechanism.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the BIOS to version 2017-05-21 or later which implements the CloseMnf protection mechanism for flash memory write protection.

Fix this in Intense Pc Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8083 — 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-2017-8083 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