# CVE-2015-5236: Security feature bypass in Icedtea-web

> Attackers can bypass Same Origin Policy restrictions in IcedTea-Web by spoofing the applet codebase attribute, allowing unauthorized cross-origin access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2022
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-5236, GHSA-f95f-r783-xxx3, UBUNTU-CVE-2015-5236

## What is CVE-2015-5236?

CVE-2015-5236 is a high-severity vulnerability in Icedtea-web, published on 7 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was discovered that the IcedTea-Web used codebase attribute of the <applet> tag on the HTML page that hosts Java applet in the Same Origin Policy (SOP) checks. As the specified codebase does not have to match the applet's actual origin, this allowed malicious site to bypass SOP via spoofed codebase value.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2015-5236?

It affects 1 product.


Products: Icedtea-Web Project Icedtea-Web.

## How do I fix CVE-2015-5236?

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

## Is CVE-2015-5236 being exploited?

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

## Other vulnerabilities in Icedtea-web

- [CVE-2019-10182](https://insights.sbomify.com/CVE-2019-10182/): Path traversal in icedtea-web (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5236 and fix it if it is affected.

What it is: CVE-2015-5236 is a high-severity vulnerability in Icedtea-web, published on 7 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5236 in the wild and no public exploit code.

Affected product: Icedtea-web. 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-2015-5236/ (Markdown: https://insights.sbomify.com/CVE-2015-5236/index.md)
```

## Sources

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

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