# CVE-2014-8471: Other in n/a

> Remote attackers can conduct replay attacks against CA Cloud Service Management, potentially bypassing security controls.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 4 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jxfw-8wjc-r4f8

## What is CVE-2014-8471?

CVE-2014-8471 is a medium-severity vulnerability in n/a, published on 4 Nov 2014. It can be exploited over the network.

### Official description

CA Cloud Service Management (CSM) before Summer 2014 allows remote attackers to conduct replay attacks via unspecified vectors.

## Which versions are affected by CVE-2014-8471?

It affects 1 product.


Products: Ca Cloud Service Management.

## How do I fix CVE-2014-8471?

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

## Is CVE-2014-8471 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-8474](https://insights.sbomify.com/CVE-2014-8474/): XML external entity in n/a (high 7.5)
- [CVE-2014-8472](https://insights.sbomify.com/CVE-2014-8472/): Auth bypass in n/a (medium 6.8)
- [CVE-2014-8473](https://insights.sbomify.com/CVE-2014-8473/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8471 and fix it if it is affected.

What it is: CVE-2014-8471 is a medium-severity vulnerability in n/a, published on 4 Nov 2014. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2014-8471 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-2014-8471/ (Markdown: https://insights.sbomify.com/CVE-2014-8471/index.md)
```

## Sources

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

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