LiveActive security incident?Get immediate response
CVE Record

CVE-2018-0040: Contrail Service Orchestration: hardcoded cryptographic certificates and keys

Juniper Networks Contrail Service Orchestrator versions prior to 4.0.0 use hardcoded cryptographic certificates and keys in some cases, which may allow network based attackers to gain unauthorized access to services.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Juniper Contrail Service Orchestration before 4.0.0 may use built-in cryptographic certificates and keys. If exposed, a remote attacker could potentially use those shared secrets to access services without authorization. The impact is rated critical because compromise could affect confidentiality, integrity, and availability.

Executive priority

Treat this as urgent for any organization using Juniper Contrail Service Orchestration. The flaw is remotely reachable, requires no authentication, and has critical potential impact. Prioritize version confirmation, management-plane exposure review, and upgrade planning.

Technical view

CVE-2018-0040 is a CWE-321 hardcoded cryptographic key issue in Juniper Networks Contrail Service Orchestration versions before 4.0.0. The CVSS 3.0 score is 9.8: network attack vector, low complexity, no privileges, no user interaction, and high CIA impact.

Likely exposure

Organizations running Juniper Networks Contrail Service Orchestration versions prior to 4.0.0 are the identified exposure group. The provided sources do not specify affected deployments, configurations, CPEs, or which services contain the hardcoded certificates and keys.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It does state that network-based attackers may gain unauthorized access to services in some cases, which makes internet or broadly reachable management-plane exposure especially concerning.

Researcher notes

Evidence is limited to the CVE record and Juniper advisory reference in the bundle. The public summary does not identify exact certificates, service names, deployment prerequisites, exploit maturity, or compensating controls beyond version-based exposure before 4.0.0.

Mitigation direction

  • Identify all Contrail Service Orchestration deployments and confirm their versions.
  • Upgrade affected installations to 4.0.0 or later, following Juniper guidance.
  • Review Juniper advisory JSA10872 for any product-specific instructions.
  • Restrict network access to orchestration and management services.
  • Rotate credentials or certificates if vendor guidance recommends it.

Validation and detection

  • Inventory Contrail Service Orchestration instances across production and non-production environments.
  • Verify whether each instance is running a version before 4.0.0.
  • Check exposure of related services from untrusted networks.
  • Review access logs for unexpected authentication or service access patterns.
  • Confirm remediation state against Juniper advisory JSA10872.
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.

cwe · low confidence lookup

CWE-321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-0040 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
Critical
CVSS
9.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.0CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

9.8Critical
CVSS 3.0 vector shape for CVE-2018-0040Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksContrail Service OrchestrationunspecifiedListed
Weakness

CWE details

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

CWE-321 · source CWE mapping

Use of Hard-coded Cryptographic Key

Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.