CVE-2022-39835
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 · uneditedAn issue was discovered in Gajim through 1.4.7. The vulnerability allows attackers, via crafted XML stanzas, to correct messages that were not sent by them. The attacker needs to be part of the group chat or single chat. The fixed version is 1.5.0.
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 confidenceGajim through version 1.4.7 contains an improper authorization vulnerability in its XMPP message correction mechanism. Attackers who are participants in a group chat or single chat can send crafted XML stanzas to correct messages they did not originally send, allowing unauthorized manipulation of message history.
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< 1.5.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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Determine installed Gajim versionOpen Gajim, then navigate to Help > About, or check your system package manager for the installed gajim package versionAffected if The displayed version is 1.4.7 or lower, or any version below 1.5.0
-
Confirm XMPP account usageCheck if Gajim is configured with an active XMPP (Jabber) account by looking at the account manager or roster windowAffected if An XMPP account is configured and active, as this is required for the vulnerable message correction feature to be in use
-
Verify message correction feature is in useInspect whether the client has the ability to correct messages (XEP-0308) - this is a standard XMPP feature enabled by default when sending messages via XMPPAffected if XMPP messaging is being used, as the vulnerability allows any chat participant to send unauthorized message correction stanzas
You are affected if Gajim version is below 1.5.0 and you use it to connect to XMPP servers for messaging.
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.
dbcve · scoped1.5.0
Upgrade Gajim to version 1.5.0 or later. Additionally, implement XMPP server-side controls to validate message correction requests against the original message sender.
Gajim 1.5.0
- Check current Gajim version installed (e.g., gajim --version or about dialog in the application)
- Upgrade Gajim to version 1.5.0 using your system's package manager (e.g., apt-get install gajim, dnf update gajim, or pacman -S gajim)
- If the package manager does not have 1.5.0 yet, download Gajim 1.5.0 from the official website or GitHub releases at https://dev.gajim.org/
- After upgrade, verify the installed version shows 1.5.0
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2022-39835 — 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-2022-39835 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