# CVE-2014-5237: Server-side request forgery in n/a

> Remote attackers can trigger server-side requests and embed arbitrary images via crafted URLs in text documents, potentially accessing internal resources.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** No
- **Published:** 1 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9c4c-qp3h-qxm5

## What is CVE-2014-5237?

CVE-2014-5237 is a medium-severity server-side request forgery vulnerability in n/a, published on 1 Dec 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Server-side request forgery (SSRF) vulnerability in the documentconverter component in Open-Xchange (OX) AppSuite before 7.4.2-rev10 and 7.6.x before 7.6.0-rev10 allows remote attackers to trigger requests to arbitrary servers and embed arbitrary images via a URL in an embedded image in a Text document, which is not properly handled by the image preview.

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

It affects 1 product.


Products: Open-Xchange App Suite.

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

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

## Is CVE-2014-5237 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-23099](https://insights.sbomify.com/CVE-2022-23099/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5237 is a medium-severity server-side request forgery vulnerability in n/a, published on 1 Dec 2014. 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-2014-5237 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-5237/ (Markdown: https://insights.sbomify.com/CVE-2014-5237/index.md)
```

## Sources

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

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