# CVE-2023-31203: Denial of service in OpenVINO Model Server software

> An unauthenticated attacker can cause a denial of service in OpenVINO Model Server via improper input validation.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Nov 2023
- **Updated:** 14 Aug 2024
- **Also known as:** GHSA-262p-h3cm-wwv8

## What is CVE-2023-31203?

CVE-2023-31203 is a medium-severity denial of service vulnerability in OpenVINO Model Server software, published on 14 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper input validation in some OpenVINO Model Server software before version 2022.3 for Intel Distribution of OpenVINO toolkit may allow an unauthenticated user to potentially enable denial of service via network access.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-31203?

It affects 1 product.


Products: Intel Openvino Model Server.

## How do I fix CVE-2023-31203?

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

## Is CVE-2023-31203 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31203 and fix it if it is affected.

What it is: CVE-2023-31203 is a medium-severity denial of service vulnerability in OpenVINO Model Server software, published on 14 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-31203 in the wild and no public exploit code.

Affected product: OpenVINO Model Server software. 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-2023-31203/ (Markdown: https://insights.sbomify.com/CVE-2023-31203/index.md)
```

## Sources

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

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