# CVE-2017-14360: MFSBGN03791 rev.1 - HPE Content Manager Workgroup Service, Denial of Service (DoS)

> Remote attackers can cause a denial of service in HPE Content Manager Workgroup Service, requiring administrators to apply vendor patches.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h5x8-4pmq-84wh

## What is CVE-2017-14360?

CVE-2017-14360 is a medium-severity denial of service vulnerability in Micro Focus HPE Content Manager Workgroup Service, published on 8 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A potential security vulnerability has been identified in HPE Content Manager Workgroup Service v9.00. The vulnerability could be remotely exploited to allow Denial of Service (DoS).

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Hp Content Manager.

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

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

## Is CVE-2017-14360 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14360 is a medium-severity denial of service vulnerability in Micro Focus HPE Content Manager Workgroup Service, published on 8 Nov 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-14360 in the wild and no public exploit code.

Affected product: Micro Focus HPE Content Manager Workgroup Service. 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-14360/ (Markdown: https://insights.sbomify.com/CVE-2017-14360/index.md)
```

## Sources

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

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