Saffron MemorybaseApplication · Intel

CVE-2018-3662

HIGH · 8.0 CVSS v3.0 Published 2018-08-01
Fix available
A fix is available. Upgrade to 11.4 or later.
See remediation →
82/100
Remediation priority · High
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
Escalation of privilege in Intel Saffron MemoryBase before version 11.4 potentially allows an authorized user of the Saffron application to execute arbitrary code as root.

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 confidence

Intel Saffron MemoryBase before version 11.4 contains a privilege escalation vulnerability where an authorized user of the application can potentially execute arbitrary code with root privileges. The flaw allows a user with standard application access to elevate their privileges to the root level on the host system.

MitigationUpgrade Intel Saffron MemoryBase to version 11.4 or later to remediate this vulnerability. Verify the upgrade in a test environment before production deployment.

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
Saffron MemorybaseApplication
Affected:< 11.4

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

CVSS:3.0/AV:A/AC:L/PR:L/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. Determine installed version of Intel Saffron MemoryBase
    Locate the installed Intel Saffron MemoryBase application and retrieve its version number. This is typically available through the application's About section, installed package information, or by querying the application directly if it provides a version command or API endpoint.
    Affected if The installed version is any version before 11.4 (for example, 11.3.x, 11.2.x, or earlier releases).
  2. Identify user account types configured in the application
    Review the user management or authentication configuration within Intel Saffron MemoryBase to identify whether standard (non-privileged) user accounts exist in the system.
    Affected if Standard user accounts with application-level access are present alongside the vulnerability in a version before 11.4.
  3. Verify application execution context
    Examine how the Intel Saffron MemoryBase service or process runs on the host system. Check if it executes with elevated or root-level system privileges.
    Affected if The application runs with root or elevated system privileges while vulnerable versions (before 11.4) are in use.
  4. Review application configuration for privilege-related settings
    Inspect the application's configuration files, settings, or policy definitions related to user permissions and execution privileges. Look for any settings that control whether standard users can invoke privileged operations or execute system-level commands.
    Affected if Configuration permits standard users to trigger privileged operations and the version is before 11.4.

You are affected if Intel Saffron MemoryBase is installed at a version earlier than 11.4 and standard user accounts exist with the ability to interact with privileged application functions.

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
Upgrade available Upgrade to 11.4 or later
Fixed in 11.4
Interim mitigation

Upgrade Intel Saffron MemoryBase to version 11.4 or later to remediate this vulnerability. Verify the upgrade in a test environment before production deployment.

Fix this in Saffron Memorybase Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-3662 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-3662 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