# CVE-2014-3088: File upload in n/a

> Authenticated users can bypass file upload restrictions in IBM Sametime Meeting Server by manipulating headers, potentially leading to remote code execution.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:N`)
- **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:** 1 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-28g2-8prg-qmrx

## What is CVE-2014-3088?

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

### Official description

stconf.nsf in IBM Sametime Meeting Server 8.5.1 relies on the client to validate the file format used in wAttach?OpenForm multipart/form-data POST requests, which allows remote authenticated users to bypass intended upload restrictions by modifying the Content-Type header and file extension, as demonstrated by replacing a text/plain .txt upload with an application/octet-stream .exe upload.

Weakness: CWE-264

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

It affects 1 product.


Products: Ibm Sametime Meeting Server.

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

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

## Is CVE-2014-3088 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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