# CVE-2019-25085: GNOME gvdb gvdb-builder.c gvdb_table_write_contents_async use after free

> A remote attacker can exploit a use-after-free flaw in GNOME gvdb to potentially execute arbitrary code.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **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:** Yes
- **Published:** 26 Dec 2022
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-25085, GHSA-362p-jc7p-cx87

## What is CVE-2019-25085?

CVE-2019-25085 is a medium-severity use after free vulnerability in GNOME gvdb, published on 26 Dec 2022. 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

A vulnerability was found in GNOME gvdb. It has been classified as critical. This affects the function gvdb_table_write_contents_async of the file gvdb-builder.c. The manipulation leads to use after free. It is possible to initiate the attack remotely. The name of the patch is d83587b2a364eb9a9a53be7e6a708074e252de14. It is recommended to apply a patch to fix this issue. The identifier VDB-216789 was assigned to this vulnerability.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2019-25085?

It affects 1 product.


Products: Gnome Gvariant Database.

## How do I fix CVE-2019-25085?

Apply the vendor's patch.

## Is CVE-2019-25085 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25085 and fix it if it is affected.

What it is: CVE-2019-25085 is a medium-severity use after free vulnerability in GNOME gvdb, published on 26 Dec 2022. 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-2019-25085 in the wild and no public exploit code.

Affected product: GNOME gvdb. 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-2019-25085/ (Markdown: https://insights.sbomify.com/CVE-2019-25085/index.md)
```

## Sources

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

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