CVE-2022-39835 json
An issue was discovered in Gajim through 1.4.7.
published 2022-09-27 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-42280
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
An 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.
Patch / fix
- gajim gajim 1.5.0
- gajim Debian 14, Debian 13, Debian 12 1.5.0-1
debian advisories DEBIAN-CVE-2022-39835
- gajim openSUSE Tumbleweed 1.5.1-1.1
opensuse advisories openSUSE-SU-2024:12354-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-39835 updated
gajim: security issue
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 17 mo ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
dev.gajim.org
/gajim/gajim/-/tags
vendor-advisory
-
dev.gajim.org
/gajim/gajim/-/blob/master/ChangeLog
release-notes, vendor-advisory
Sources
- CVE List CVE-2022-39835
- NVD CVE-2022-39835
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.