# CVE-2017-10616: Contrail: hard coded credentials

> Hardcoded credentials in the ifmap service allow attackers to access sensitive data in Juniper Contrail deployments.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hhp8-q7c4-jx53

## What is CVE-2017-10616?

CVE-2017-10616 is a medium-severity vulnerability in Juniper Networks Contrail, published on 13 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ifmap service that comes bundled with Juniper Networks Contrail releases uses hard coded credentials. Affected releases are Contrail releases 2.2 prior to 2.21.4; 3.0 prior to 3.0.3.4; 3.1 prior to 3.1.4.0; 3.2 prior to 3.2.5.0. CVE-2017-10616 and CVE-2017-10617 can be chained together and have a combined CVSSv3 score of 5.8 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N).

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

## Which versions are affected by CVE-2017-10616?

It affects 1 product.


Products: Juniper Contrail.

## How do I fix CVE-2017-10616?

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

## Is CVE-2017-10616 being exploited?

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

## Other vulnerabilities in Juniper Networks Contrail

- [CVE-2017-10617](https://insights.sbomify.com/CVE-2017-10617/): Contrail: XML External Entity (XXE) vulnerability (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10616 and fix it if it is affected.

What it is: CVE-2017-10616 is a medium-severity vulnerability in Juniper Networks Contrail, published on 13 Oct 2017. 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-2017-10616 in the wild and no public exploit code.

Affected product: Juniper Networks Contrail. 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-2017-10616/ (Markdown: https://insights.sbomify.com/CVE-2017-10616/index.md)
```

## Sources

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

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