# CVE-2017-1000360: OpenDaylight NULL Pointer Dereference

> A null pointer dereference in the OpenDaylight xsql module causes exceptions and potential service disruption.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gjq3-997p-hg6f

## What is CVE-2017-1000360?

CVE-2017-1000360 is a medium-severity vulnerability in n/a, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

StreamCorruptedException and NullPointerException in OpenDaylight odl-mdsal-xsql. Controller launches exceptions in the console. Component: OpenDaylight odl-mdsal-xsql is vulnerable to this flaw. Version: The tested versions are OpenDaylight 3.3 and 4.0.

Weakness: CWE-476 (NULL Pointer Dereference)

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

2 open source packages ship an affected version, including org.opendaylight.controller:releasepom. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.opendaylight.controller:releasepom` | Maven | All versions to 4.0 | None |
| `org.opendaylight.controller:releasepom` | Maven | All versions to 4.0 | None |

Products: Opendaylight Opendaylight.

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

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

## Is CVE-2017-1000360 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1778](https://insights.sbomify.com/CVE-2015-1778/): Opendaylight will authenticate any username and password combination (critical 9.8)
- [CVE-2017-1000411](https://insights.sbomify.com/CVE-2017-1000411/): Denial of service in n/a (high 7.5)
- [CVE-2017-1000357](https://insights.sbomify.com/CVE-2017-1000357/): Denial of service in n/a (high 7.5)
- [CVE-2017-1000361](https://insights.sbomify.com/CVE-2017-1000361/): OpenDaylight Controller DoS (high 7.5)
- [CVE-2014-5035](https://insights.sbomify.com/CVE-2014-5035/): XML external entity in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000360 is a medium-severity vulnerability in n/a, published on 24 Apr 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-1000360 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.opendaylight.controller:releasepom (Maven): affected all versions up to 4.0; no fix listed
- org.opendaylight.controller:releasepom (Maven): affected all versions up to 4.0; no fix listed

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-1000360/ (Markdown: https://insights.sbomify.com/CVE-2017-1000360/index.md)
```

## Sources

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

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