dbcve.org
Contrail Service OrchestrationApplication · Juniper

CVE-2018-0039

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-11
Fix available
A fix is available. Upgrade to 4.0.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 4.0.0 have Grafana service enabled by default with hardcoded credentials. These credentials allow network based attackers unauthorized access to information stored in Grafana or exploit other weaknesses or vulnerabilities in Grafana.

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 releases prior to 4.0.0 ship with Grafana service enabled by default using hardcoded credentials. Attackers with network access can authenticate to Grafana without legitimate credentials, potentially accessing stored metrics/dashboards and exploiting known Grafana vulnerabilities.

MitigationUpgrade to Contrail Service Orchestration 4.0.0 or later which removes the hardcoded credentials, or immediately change the default Grafana password and restrict network access to the Grafana service.

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:< 4.0.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 version
    Run the command to display the installed Contrail Service Orchestration version (for example, 'contrail-version' or check the package version via your package manager)
    Affected if The version is below 4.0.0
  2. Verify Grafana service status
    Check if the Grafana service is running on the Contrail system (for example, 'systemctl status grafana' or similar service status command)
    Affected if Grafana service is enabled and running on the affected Contrail version
  3. Confirm default Grafana credentials are in use
    Locate the Grafana configuration file and inspect the admin username and password settings to determine if they match the known hardcoded defaults
    Affected if The default hardcoded credentials have not been changed from the factory defaults
  4. Assess Grafana network exposure
    Check which network interfaces and ports Grafana is listening on (for example, netstat or ss output for port 3000, the default Grafana port)
    Affected if Grafana is accessible on a network interface reachable from untrusted networks

You are affected if running Contrail Service Orchestration version below 4.0.0 with Grafana service enabled using the default hardcoded credentials and 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 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Upgrade to Contrail Service Orchestration 4.0.0 or later which removes the hardcoded credentials, or immediately change the default Grafana password and restrict network access to the Grafana service.

Recommended fix High confidence

Contrail Service Orchestration 4.0.0 or later

  1. Identify current Contrail Service Orchestration version using 'contrail-version' or Junos CLI commands
  2. Review upgrade prerequisites and compatibility matrix in Juniper documentation at kb.juniper.net
  3. Create a complete backup of current configuration and database
  4. Schedule maintenance window for upgrade procedure
  5. Upgrade Contrail Service Orchestration to version 4.0.0 or later following Juniper's documented upgrade procedure
  6. After upgrade, verify Grafana service is running with non-default credentials
  7. Confirm upgrade success by checking Contrail services status with 'contrail-status'
Caveat Review Juniper upgrade guide for known issues between pre-4.0.0 and 4.0.0 versions; ensure compatibility with underlying Junos and OpenStack versions

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-0039 — 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-0039 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