# CVE-2010-3918: Other in n/a

> Remote attackers can read or modify clipboard contents via a crafted website due to lack of isolation between web scripts and the clipboard.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Dec 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6fwx-49rw-q8pv

## What is CVE-2010-3918?

CVE-2010-3918 is a medium-severity vulnerability in n/a, published on 10 Dec 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Fenrir Sleipnir 2.9.6 and earlier does not prevent interaction between web script and the clipboard, which allows remote attackers to read or modify the clipboard contents via a crafted web site.

Weakness: CWE-264

## Which versions are affected by CVE-2010-3918?

It affects 1 product.


Products: Fenrir-Inc Sleipnir.

## How do I fix CVE-2010-3918?

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

## Is CVE-2010-3918 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-7831](https://insights.sbomify.com/CVE-2016-7831/): Open redirect in Sleipnir 4 Black Edition for Mac (medium 6.1)
- [CVE-2013-2303](https://insights.sbomify.com/CVE-2013-2303/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3918 and fix it if it is affected.

What it is: CVE-2010-3918 is a medium-severity vulnerability in n/a, published on 10 Dec 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-3918 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-2010-3918/ (Markdown: https://insights.sbomify.com/CVE-2010-3918/index.md)
```

## Sources

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

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