Skip to content
Fencer Intel
low 1.9

CVE-2013-4509 json

The default configuration of IBUS 1.5.4, and possibly 1.5.2 and earlier, when IBus.InputPurpose.PASSWORD is not set and used with GNOME 3,…

published 12y ago modified 4mo ago also EUVD-2013-4370

cvss
1.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

The default configuration of IBUS 1.5.4, and possibly 1.5.2 and earlier, when IBus.InputPurpose.PASSWORD is not set and used with GNOME 3, does not obscure the entered password characters, which allows physically proximate attackers to obtain a user password by reading the lockscreen.

Patch / fix

  • mozc Debian 14, Debian 13, Debian 12 1.12.1599.102-1
  • ibus-anthy Debian 14, Debian 13, Debian 12 1.5.4-1
  • ibus-pinyin Debian 14, Debian 13, Debian 12 1.5.0-1
  • ibus-chewing Debian 14, Debian 13, Debian 12 1.4.3-4

debian advisories DEBIAN-CVE-2013-4509

Is CVE-2013-4509 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 Fencer

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-2013-4509 updated cvss 1.9

ibus: visible password entry flaw

  • Red Hat Enterprise Linux 6 ibus-anthy, ibus-pinyin, ibus-chewing, ibus-pinyin-open-phrase Red Hat Enterprise Linux 7 ibus-chewing
    not 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

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-255 Credentials Management Errors

References

Sources

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.