dbcve.org
SysinfoApplication · Magnicomp

CVE-2018-9310

HIGH · 7.8 CVSS v3.0 Published 2018-04-30
Fix available
A fix is available. Upgrade to after 10-h81 or later.
See remediation →
80/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
An issue was discovered in MagniComp SysInfo before 10-H82 if setuid root (the default). This vulnerability allows any local user on a Linux/UNIX system to run SysInfo and obtain a root shell, which can be used to compromise the local system.

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

MagniComp SysInfo versions before 10-H82 ship with setuid root permissions by default. This allows any local user on the system to execute the binary and leverage a privilege escalation flaw to obtain a root shell, fully compromising the local system.

MitigationUpgrade MagniComp SysInfo to version 10-H82 or later. If the setuid functionality is not required, consider removing the setuid bit after upgrading to reduce the attack surface.

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
SysinfoApplication
Affected:>= 10-h76, <= 10-h81

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

CVSS:3.0/AV:L/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. Locate the MagniComp SysInfo binary
    Run 'find / -name sysinfo* -o -name mcsi* 2>/dev/null' or check common locations like /usr/bin, /usr/sbin, /opt/magnicomp
    Affected if The binary exists on the system
  2. Check the installed version
    Run the binary with --version or -v flag, or check RPM/DEB package info with 'rpm -qi' or 'dpkg -l' for the package name containing 'sysinfo' or 'magnicomp'
    Affected if Version is between 10-h76 and 10-h81 inclusive
  3. Verify setuid root permissions
    Run 'ls -la <path_to_binary>' and look for 's' in the owner execute field (e.g., -rwsr-xr-x)
    Affected if The setuid bit is set and owned by root
  4. Confirm world-executable permissions
    Check the file permissions - if others have execute permission (last three characters include 'x'), any local user can run it
    Affected if The binary is executable by all users (o+x permission)

A user is affected if MagniComp SysInfo version 10-h76 through 10-h81 is installed with the setuid bit enabled, allowing any local user to execute it and potentially escalate privileges.

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 a release after 10-h81
Interim mitigation

Upgrade MagniComp SysInfo to version 10-H82 or later. If the setuid functionality is not required, consider removing the setuid bit after upgrading to reduce the attack surface.

Fix this in Sysinfo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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