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

> Hardcoded credentials in Juniper Contrail Service Orchestration allow network attackers unauthorized access to Keystone service information.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2gw3-mxrj-jwhh

## What is CVE-2018-0041?

CVE-2018-0041 is a critical vulnerability in Juniper Networks Contrail Service Orchestration, published on 11 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2018-0041?

It affects 1 product.


Products: Juniper Contrail Service Orchestration.

## How do I fix CVE-2018-0041?

No fix has been published for CVE-2018-0041 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-0041 being exploited?

There is no known exploitation of CVE-2018-0041 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Networks Contrail Service Orchestration

- [CVE-2018-0038](https://insights.sbomify.com/CVE-2018-0038/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-0040](https://insights.sbomify.com/CVE-2018-0040/): Contrail Service Orchestration: hardcoded cryptographic certificates and keys (critical 9.8)
- [CVE-2018-0042](https://insights.sbomify.com/CVE-2018-0042/): Juniper Networks CSO versions prior to 4.0.0 may log passwords in log files leading to an information disclosure vulnerability. (critical 9.8)
- [CVE-2022-22152](https://insights.sbomify.com/CVE-2022-22152/): Contrail Service Orchestration: Tenants able to see other tenants policies via REST API interface (high 7.7)
- [CVE-2022-22189](https://insights.sbomify.com/CVE-2022-22189/): Privilege escalation in Contrail Service Orchestration (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0041 and fix it if it is affected.

What it is: CVE-2018-0041 is a critical vulnerability in Juniper Networks Contrail Service Orchestration, published on 11 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0041 in the wild and no public exploit code.

Affected product: Juniper Networks Contrail Service Orchestration. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-0041/ (Markdown: https://insights.sbomify.com/CVE-2018-0041/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0041
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0041
- OSV: https://osv.dev/vulnerability/CVE-2018-0041

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-0041/
Summaries are generated and may contain mistakes; the official description above is the record.
