# CVE-2017-9773: Denial of service in n/a

> Attackers can cause a denial of service in the Horde_Image library by sending a crafted URL to the Null image driver.

- **Severity:** Medium 5.7 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-9773, GHSA-gffm-74c3-652g, UBUNTU-CVE-2017-9773

## What is CVE-2017-9773?

CVE-2017-9773 is a medium-severity denial of service vulnerability in n/a, published on 21 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Denial of Service was found in Horde_Image 2.x before 2.5.0 via a crafted URL to the "Null" image driver.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Horde Horde Image.

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

Upgrade to a fixed version.

## Is CVE-2017-9773 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9773 is a medium-severity denial of service vulnerability in n/a, published on 21 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-9773 in the wild and no public exploit code.

Affected product: n/a. 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-9773/ (Markdown: https://insights.sbomify.com/CVE-2017-9773/index.md)
```

## Sources

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

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