# CVE-2021-42522: Information disclosure in GNOME anjuta

> An information disclosure vulnerability in GNOME Anjuta allows attackers to read sensitive memory data due to a missing memory free call in the document manager plugin.

- **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:** 25 Aug 2022
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-42522, GHSA-mxvm-wqqj-9w63, UBUNTU-CVE-2021-42522

## What is CVE-2021-42522?

CVE-2021-42522 is a high-severity vulnerability in GNOME anjuta, published on 25 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a Information Disclosure vulnerability in anjuta/plugins/document-manager/anjuta-bookmarks.c. This issue was caused by the incorrect use of libxml2 API. The vendor forgot to call 'g_free()' to release the return value of 'xmlGetProp()'.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-42522?

It affects 1 product.


Products: Gnome Anjuta.

## How do I fix CVE-2021-42522?

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

## Is CVE-2021-42522 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42522 and fix it if it is affected.

What it is: CVE-2021-42522 is a high-severity vulnerability in GNOME anjuta, published on 25 Aug 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-2021-42522 in the wild and no public exploit code.

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

## Sources

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

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