CVE-2020-35450 json
Gobby 0.4.11 allows a NULL pointer dereference in the D-Bus handler for certain set_language calls.
published 5y ago modified 4mo ago also EUVD-2020-23124
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Gobby 0.4.11 allows a NULL pointer dereference in the D-Bus handler for certain set_language calls.
Patch / fix
- gobby Debian 14, Debian 13, Debian 12 0.6.0~20201227~b98f4d2-1
debian advisories DEBIAN-CVE-2020-35450
- gobby Arch Linux 1:0.5.0+116+g295e697-1
arch linux advisories AVG-1383
- github.com/gobby/gobby#184 pull request
Is CVE-2020-35450 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-35450 updated cvss 5.3
gobby: NULL pointer dereference in the D-Bus handler for certain set_language calls
-
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
Exploit prediction
1.42% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/gobby/gobby/pull/184 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/gobby/gobby/pull/184
exploit, patch, third-party-advisory
Sources
- CVE List CVE-2020-35450
- NVD CVE-2020-35450
Fencer Intel 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.