CVE-2021-42522
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere 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()'.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA memory leak in Anjuta IDE's bookmark manager (anjuta-bookmarks.c) occurs because the return value of libxml2's xmlGetProp() is not freed with g_free(). This causes progressive memory accumulation leading to information disclosure through potential out-of-memory conditions or exposure of sensitive data in unreleased memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Anjuta IDE installation and versionRun 'anjuta --version' or check your package manager for the installed Anjuta versionAffected if The installed version is 2.0.0 exactly, as this is the only affected version listed
-
Locate the bookmark manager source fileSearch for 'anjuta-bookmarks.c' in the source code or compiled binary if you have access: find / -name 'anjuta-bookmarks.c' 2>/dev/null or check the binary for the string 'anjuta-bookmarks'Affected if The file exists and is part of your Anjuta installation
-
Check for unpatched memory leak pattern in sourceIf source code is available, search for xmlGetProp calls in anjuta-bookmarks.c and verify if corresponding g_free() calls are missing on the returned xmlChar* valuesAffected if The code contains xmlGetProp() calls without corresponding g_free() calls to release the returned string memory
-
Monitor for memory growth during bookmark operationsUse process memory monitoring tools such as 'psrecord' or system monitors while repeatedly loading/saving bookmarks in Anjuta to observe memory usage patternsAffected if Memory usage progressively increases without stabilization during repeated bookmark manager operations
-
Verify bookmark manager plugin is loadedCheck if the bookmarks plugin is enabled in Anjuta: look for 'bookmarks' in the plugin list or attempt to access the bookmarks feature through the UI (View > Bookmarks or similar)Affected if The bookmarks plugin is active and being used, as the vulnerability only triggers when the bookmark manager code path executes
You are affected if Anjuta version 2.0.0 is installed and the bookmark manager feature is in use, with the vulnerable xmlGetProp/g_free pattern present in the code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAdd g_free() call to release the dynamically allocated string returned by xmlGetProp() after its value has been used in the affected code path.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-42522 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-42522 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data