# CVE-2015-8079: Information disclosure in n/a

> Qt WebKit library leaks private browsing URLs to the favicon database, allowing attackers to read sensitive browsing history.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** Yes
- **Published:** 7 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wwwx-88mv-pg56, UBUNTU-CVE-2015-8079

## What is CVE-2015-8079?

CVE-2015-8079 is a medium-severity vulnerability in n/a, published on 7 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

qt5-qtwebkit before 5.4 records private browsing URLs to its favicon database, WebpageIcons.db.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Qt Qtwebkit.

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

Upgrade to a fixed version.

## Is CVE-2015-8079 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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