# CVE-2014-0868: Business logic in n/a

> Authenticated attackers can bypass dual-control restrictions and modify read-only limit data by submitting crafted XML documents, undermining credit limit integrity.

- **Severity:** Medium 4.9 (`AV:N/AC:M/Au:S/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wg8v-cggr-5vm6

## What is CVE-2014-0868?

CVE-2014-0868 is a medium-severity vulnerability in n/a, published on 7 Jul 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RICOS in IBM Algo Credit Limits (aka ACLM) 4.5.0 through 4.7.0 before 4.7.0.03 FP5 in IBM Algorithmics relies on client-side input validation, which allows remote authenticated users to bypass intended dual-control restrictions and modify data via a crafted XML document, as demonstrated by manipulation of read-only limit data.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Ibm Algo Credit Limits, Ibm Algorithmics.

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

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

## Is CVE-2014-0868 being exploited?

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

Public exploit code:

- IBM Algorithmics RICOS 4.5.0 < 4.7.0 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-0864](https://insights.sbomify.com/CVE-2014-0864/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-0867](https://insights.sbomify.com/CVE-2014-0867/): Other in n/a (medium 5.8)
- [CVE-2014-0865](https://insights.sbomify.com/CVE-2014-0865/): Deserialization in n/a (medium 4.9)
- [CVE-2014-0866](https://insights.sbomify.com/CVE-2014-0866/): Information disclosure in n/a (medium 4.3)
- [CVE-2014-0869](https://insights.sbomify.com/CVE-2014-0869/): Weak cryptography in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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