LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1000047: rbenv (all current versions) is vulnerable to Directory Traversal in the specification of Ruby version resu...

rbenv (all current versions) is vulnerable to Directory Traversal in the specification of Ruby version resulting in arbitrary code execution

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

rbenv, a Ruby version management tool, is reported vulnerable to directory traversal in how a Ruby version is specified. The CVE description says this can lead to arbitrary code execution. Business risk is highest where developers or automation run rbenv against untrusted repositories or project files.

Executive priority

Treat this as a targeted developer-tooling risk, not a broad internet-facing emergency. Prioritize teams using rbenv in CI or with third-party code because compromise could affect source code, credentials, or build outputs.

Technical view

CVE-2017-1000047 describes directory traversal through the Ruby version specification in rbenv, affecting “all current versions” per the CVE text. The provided record does not include CVSS, CWE, exact affected versions, patch details, or vendor remediation guidance.

Likely exposure

Exposure is most likely on developer workstations, CI jobs, build systems, or automation that use rbenv and process repository-controlled Ruby version configuration. The source bundle does not identify specific packaged versions, platforms, or downstream distributions.

Exploitation context

The source bundle does not show KEV listing or cited active exploitation. The reported impact is arbitrary code execution, but exploitation prerequisites and reliability are not documented in the provided CVE metadata.

Researcher notes

Evidence is sparse: the CVE record names rbenv and arbitrary code execution, but affected versions and fixes are not structured. Use the advisory as the primary technical lead and avoid assuming exploit activity without additional sourced evidence.

Mitigation direction

  • Inventory developer, CI, and build environments using rbenv.
  • Review the linked advisory and current rbenv project guidance.
  • Avoid running rbenv against untrusted repositories until risk is resolved.
  • Pin or update rbenv according to confirmed upstream guidance.
  • Restrict build automation permissions and isolate untrusted project processing.

Validation and detection

  • Search managed endpoints and CI images for rbenv installations.
  • Identify workflows that read repository-controlled Ruby version files.
  • Check whether rbenv versions match any advisory guidance.
  • Review CI logs for untrusted repositories invoking rbenv.
  • Document compensating controls where patch status is unclear.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-1000047 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.