# CVE-2008-7298: Security feature bypass in n/a

> Man-in-the-middle attackers can overwrite or delete HTTPS cookies in the Android browser due to missing HSTS support, requiring user interaction.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/I:P/A:P`)
- **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:** 9 Aug 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w454-mc57-3f76

## What is CVE-2008-7298?

CVE-2008-7298 is a medium-severity vulnerability in Google Android, published on 9 Aug 2011. 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

The Android browser in Android cannot properly restrict modifications to cookies established in HTTPS sessions, which allows man-in-the-middle attackers to overwrite or delete arbitrary cookies via a Set-Cookie header in an HTTP response, related to lack of the HTTP Strict Transport Security (HSTS) includeSubDomains feature, aka a "cookie forcing" issue.

Weakness: CWE-264

## Which versions are affected by CVE-2008-7298?

It affects 2 products.


Products: Android Android Browser, Google Android.

## How do I fix CVE-2008-7298?

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

## Is CVE-2008-7298 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7298 and fix it if it is affected.

What it is: CVE-2008-7298 is a medium-severity vulnerability in Google Android, published on 9 Aug 2011. 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-2008-7298 in the wild and no public exploit code.

Affected product: Google Android. 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-2008-7298/ (Markdown: https://insights.sbomify.com/CVE-2008-7298/index.md)
```

## Sources

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

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