CloudformsApplication · Redhat

CVE-2018-10905

HIGH · 7.8 CVSS v3.0 Published 2018-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
CloudForms Management Engine (cfme) is vulnerable to an improper security setting in the dRuby component of CloudForms. An attacker with access to an unprivileged local shell could use this flaw to execute commands as a high privileged user.

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

CloudForms Management Engine contains an improper security setting in its dRuby distributed Ruby component. An attacker with local shell access can exploit this misconfiguration to execute arbitrary commands as a highly privileged user (likely the cfme service account or root).

MitigationRestrict dRuby to secure settings by binding to localhost only, enabling authentication, or disabling the service if not required; then verify the configuration prevents unprivileged local access.

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
CloudformsApplication
Affected:= 4.5= 4.6
Cloudforms Management EngineApplication
Affected:= 5.8= 5.9

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. Identify installed CloudForms/ManageIQ version
    Run command to check the installed package version, such as 'rpm -q cfme' or 'rpm -q manageiq' depending on the installation, or check the about page in the web UI
    Affected if The installed version matches 4.5, 4.6, 5.8, or 5.9 of Red Hat CloudForms or CloudForms Management Engine
  2. Verify dRuby service is running
    Check if the evm service or dRuby-related process is active by running 'systemctl status evm' or 'ps aux | grep druby'
    Affected if The dRuby component (evm service) is running and accessible
  3. Check dRuby bind address configuration
    Examine the dRuby configuration files or environment variables that control the bind address; look for settings like DRUBY_BIND_ADDR or similar in the configuration
    Affected if The dRuby service is bound to 0.0.0.0 or an external interface rather than localhost only (127.0.0.1)
  4. Inspect dRuby authentication settings
    Review the dRuby configuration for authentication requirements; check if the service allows unauthenticated method calls
    Affected if Authentication is disabled or not required for dRuby communications
  5. Verify network listening ports
    Run 'netstat -tlnp' or 'ss -tlnp' and look for ports associated with the cfme/evm service, particularly the dRuby port
    Affected if The dRuby port is listening on all interfaces (0.0.0.0) rather than only localhost

You are affected if you are running version 4.5, 4.6, 5.8, or 5.9 AND the dRuby service is bound to a non-localhost address or has authentication disabled, allowing unprivileged local access.

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

Restrict dRuby to secure settings by binding to localhost only, enabling authentication, or disabling the service if not required; then verify the configuration prevents unprivileged local access.

Fix this in Cloudforms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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