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

> Remote authenticated users can crash the HTCondor scheduler daemon by exploiting GSI and VOMS extensions, requiring an upgrade to fix.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-16816, GHSA-9x52-5xwr-hfwc, UBUNTU-CVE-2017-16816

## What is CVE-2017-16816?

CVE-2017-16816 is a medium-severity denial of service vulnerability in n/a, published on 5 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The condor_schedd component in HTCondor before 8.6.8 and 8.7.x before 8.7.5 allows remote authenticated users to cause a denial of service (daemon crash) by leveraging use of GSI and VOMS extensions.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Wisc Htcondor.

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

Upgrade to a fixed version.

## Is CVE-2017-16816 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-25311](https://insights.sbomify.com/CVE-2021-25311/): Path traversal in n/a (critical 9.9)
- [CVE-2021-45102](https://insights.sbomify.com/CVE-2021-45102/): Auth bypass in n/a (high 8.8)
- [CVE-2021-25312](https://insights.sbomify.com/CVE-2021-25312/): Auth bypass in n/a (high 8.8)
- [CVE-2014-8126](https://insights.sbomify.com/CVE-2014-8126/): Code injection in HTCondor (high 8.8)
- [CVE-2012-3490](https://insights.sbomify.com/CVE-2012-3490/): Privilege escalation in Condor (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16816 is a medium-severity denial of service vulnerability in n/a, published on 5 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16816 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-16816/ (Markdown: https://insights.sbomify.com/CVE-2017-16816/index.md)
```

## Sources

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

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