dbcve.org
SatelliteApplication · Redhat

CVE-2017-2667

HIGH · 8.1 CVSS v3.1 Published 2018-03-12
Fix available
A fix is available. Upgrade to 0.10.0 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Hammer CLI, a CLI utility for Foreman, before version 0.10.0, did not explicitly set the verify_ssl flag for apipie-bindings that disable it by default. As a result the server certificates are not checked and connections are prone to man-in-the-middle attacks.

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

Hammer CLI for Foreman versions before 0.10.0 did not explicitly enable SSL certificate verification in apipie-bindings. Since apipie-bindings disables verify_ssl by default, all API connections made by Hammer CLI failed to validate server certificates, allowing attackers to intercept traffic via man-in-the-middle attacks.

MitigationUpgrade Hammer CLI to version 0.10.0 or later, which explicitly sets verify_ssl=true to ensure proper SSL/TLS certificate validation for all API communications.

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
SatelliteApplication
Affected:= 6.3
Satellite CapsuleApplication
Affected:= 6.3
Hammer CliApplication
Affected:< 0.10.0

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

CVSS:3.1/AV:N/AC:H/PR:N/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 Hammer CLI installation and version
    Run 'hammer --version' or 'rpm -q hammer-cli' to find the installed Hammer CLI version
    Affected if The version is less than 0.10.0
  2. Identify apipie-bindings version
    Run 'rpm -q apipie-bindings' to determine the apipie-bindings package version
    Affected if The package is present and linked to Hammer CLI below 0.10.0
  3. Check Hammer CLI configuration for SSL verification settings
    Examine /etc/hammer/cli_config.yml or ~/.hammer/cli_config.yml for verify_ssl or ssl_verify settings - look for verify_ssl: false, verify_ssl: true, or missing verify_ssl configuration
    Affected if verify_ssl is explicitly set to false OR is absent (defaulting to false) in the configuration files
  4. Check Red Hat Satellite or Capsule version
    Run 'satellite --version' or 'capsule-certs-generate' output, or check /etc/redhat-release for Satellite version 6.3
    Affected if Red Hat Satellite or Capsule version equals 6.3 and uses the vulnerable Hammer CLI version

You are affected if Hammer CLI version is below 0.10.0 OR if verify_ssl is not explicitly set to true in the Hammer CLI configuration, allowing unvalidated API connections.

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 0.10.0 or later
Fixed in 0.10.0
Interim mitigation

Upgrade Hammer CLI to version 0.10.0 or later, which explicitly sets verify_ssl=true to ensure proper SSL/TLS certificate validation for all API communications.

Fix this in Satellite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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