CVE-2018-0041
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 · uneditedJuniper 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.
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 confidenceJuniper Networks Contrail Service Orchestration releases prior to 3.3.0 contain hardcoded credentials embedded in the software code that are used to authenticate to the Keystone identity service. An attacker with network access can discover and use these credentials to impersonate legitimate users and access sensitive information stored within Keystone.
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< 3.3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Contrail Service Orchestration installationRun 'rpm -qa | grep contrail-service-orchestration' or check the installed packages on the system. Also check if /opt/contrail/service_orchestration exists.Affected if The package is installed and the version cannot be determined or is below 3.3.0
-
Check installed versionRun 'rpm -qi contrail-service-orchestration' or check the version in the package manager. Compare the version number against 3.3.0.Affected if The installed version is lower than 3.3.0
-
Locate hardcoded Keystone credentials in codebaseSearch the Contrail Service Orchestration installation directory (typically /opt/contrail/) for strings matching Keystone credentials, authentication tokens, or password patterns. Use 'grep -r "keystone" /opt/contrail/service_orchestration/' and examine configuration files for embedded passwords.Affected if Hardcoded credentials for Keystone authentication are found in the code or configuration files
-
Verify Keystone service exposureCheck if port 35357 or 5000 (Keystone API ports) is listening and accessible. Use 'netstat -tulpn | grep -E "(35357|5000)"' and verify network accessibility.Affected if Keystone service ports are open and reachable from untrusted networks
-
Review network access to KeystoneCheck firewall rules and network segmentation around the Contrail/Keystone infrastructure. Identify if the Keystone service is accessible from networks outside the trusted management segment.Affected if Keystone is accessible from network segments without proper access controls
You are affected if Contrail Service Orchestration version is below 3.3.0 and hardcoded Keystone credentials exist in the deployment, especially if Keystone is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.3.0
Upgrade Contrail Service Orchestration to version 3.3.0 or later, which removes the hardcoded credentials. If immediate upgrade is not possible, implement network segmentation and monitoring to restrict unauthorized access to the Keystone service.
Contrail Service Orchestration 3.3.0 or later
- Identify the current version of Contrail Service Orchestration in use
- Review the upgrade documentation and release notes at kb.juniper.net
- Plan and schedule a maintenance window for the upgrade procedure
- Perform a complete backup of all configurations and critical data
- Upgrade Contrail Service Orchestration to version 3.3.0 or later following the official upgrade guide
- After upgrade, verify the hardcoded credentials vulnerability has been addressed
- Confirm normal operation and functionality post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2018-0041 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-0041 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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