dbcve.org
Contrail Service OrchestrationApplication · Juniper

CVE-2018-0038

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-11
Fix available
A fix is available. Upgrade to 3.3.0 or later.
See remediation →
100/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
Juniper Networks Contrail Service Orchestration releases prior to 3.3.0 have Cassandra service enabled by default with hardcoded credentials. These credentials allow network based attackers unauthorized access to information stored in Cassandra.

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

Juniper Networks Contrail Service Orchestration versions prior to 3.3.0 ship with the Cassandra database service enabled by default using hardcoded credentials. Network-based attackers can exploit these static credentials to authenticate to the Cassandra service without authorization and access sensitive data stored in the database.

MitigationUpgrade to Contrail Service Orchestration 3.3.0 or later which removes the default hardcoded Cassandra credentials. If immediate upgrade is not feasible, change the default Cassandra credentials and implement network access controls to restrict Cassandra port access to authorized systems only.

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
Contrail Service OrchestrationApplication
Affected:< 3.3.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/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 Contrail Service Orchestration installation and version
    Locate the Contrail Service Orchestration installation directory and check the version file or use the product's command-line interface to query the installed version.
    Affected if The installed version is prior to 3.3.0.
  2. Verify Cassandra service is running and network-exposed
    Check for the Cassandra process running on the system and identify if it is listening on network interfaces (typically port 9042 or 7000). Use commands like 'netstat' or 'ss' to list listening ports.
    Affected if Cassandra is running and bound to a network interface accessible to untrusted networks.
  3. Locate Cassandra configuration files
    Find the Cassandra configuration directory (commonly under the Contrail installation path, typically in a 'conf' or 'etc' subdirectory) and examine the cassandra.yaml or cassandra-env.sh files.
    Affected if Configuration files exist and contain hardcoded username/password entries.
  4. Check for default Cassandra credentials in use
    Examine the Cassandra authentication configuration. If 'authenticator' is set to 'PasswordAuthenticator', inspect the configuration for default user accounts such as 'cassandra' with default passwords.
    Affected if The default Cassandra user account exists with a default or easily guessable password still in place.
  5. Verify network access controls on Cassandra port
    Review firewall rules, iptables, or network ACLs to determine if the Cassandra port (9042/7000) is accessible from untrusted network segments.
    Affected if Cassandra port is accessible from networks that should not have database access.

The environment is affected if Contrail Service Orchestration version is prior to 3.3.0 AND the Cassandra service is running with default hardcoded credentials accessible over the network.

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.

dbcve · scoped
Upgrade available Upgrade to 3.3.0 or later
Fixed in 3.3.0
Interim mitigation

Upgrade to Contrail Service Orchestration 3.3.0 or later which removes the default hardcoded Cassandra credentials. If immediate upgrade is not feasible, change the default Cassandra credentials and implement network access controls to restrict Cassandra port access to authorized systems only.

Recommended fix High confidence

3.3.0 or later

  1. Upgrade Contrail Service Orchestration to version 3.3.0 or later to resolve the hardcoded Cassandra credentials vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Contrail Service Orchestration Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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