LiveActive security incident?Get immediate response
CVE Record

CVE-2018-0041: Contrail Service Orchestration: Hardcoded credentials for Keystone service.

Juniper Networks Contrail Service Orchestration releases prior to 3.3.0 use hardcoded credentials to access Keystone service. These credentials allow network based attackers unauthorized access to information stored in keystone.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Juniper Contrail Service Orchestration before 3.3.0 contained hardcoded credentials for Keystone access. A network-based attacker could use those credentials to access information stored in Keystone without authorization. The CVSS score is critical because no prior login or user interaction is required.

Executive priority

Treat this as urgent for any organization using the affected Juniper product. The issue can expose identity-service data and potentially broader cloud-control functions, but priority depends on whether legacy CSO versions remain deployed.

Technical view

CVE-2018-0041 is a CWE-798 hardcoded credential flaw in Juniper Networks Contrail Service Orchestration releases prior to 3.3.0. The CVSS 3.0 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating remotely reachable, low-complexity compromise with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to environments running Juniper Networks Contrail Service Orchestration before 3.3.0, especially where attackers can reach Keystone-related service interfaces over the network.

Exploitation context

The provided sources describe network-based unauthorized Keystone access but do not provide evidence of active exploitation. The bundle marks KEV as false, so do not treat this as confirmed exploited from these sources alone.

Researcher notes

Evidence is concise and official but limited in the supplied bundle. The key facts are affected product, versions prior to 3.3.0, hardcoded Keystone credentials, critical CVSS 9.8, and no KEV listing. Do not infer additional affected Juniper products or public exploit activity.

Mitigation direction

  • Upgrade affected Contrail Service Orchestration deployments to 3.3.0 or later.
  • Review Juniper JSA10872 for vendor-specific remediation and operational guidance.
  • Restrict network access to Keystone and orchestration interfaces to trusted management networks.
  • Rotate any credentials that may overlap with affected Keystone service access.
  • Monitor Keystone authentication and authorization events for unexpected service-account use.

Validation and detection

  • Inventory all Contrail Service Orchestration deployments and record exact versions.
  • Confirm no production instance is running a release prior to 3.3.0.
  • Verify Keystone endpoints are not reachable from untrusted networks.
  • Review Keystone logs for unexplained access around the exposure window.
  • Confirm remediation status against Juniper advisory JSA10872.
Prepared
Confidence
high
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 · medium confidence lookup

CWE-798: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-0041 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-0041Attack 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-798 · source CWE mapping

Use of Hard-coded Credentials

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