It was discovered that libXfont incorrectly followed symlinks when opening
font files. A local unprivileged user could use this issue to cause the X
server to access arbitrary files, including special device files.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
Ubuntu | 17.10 | noarch | libxfont1 | < 1:1.5.2-4ubuntu1.1 | UNKNOWN |
Ubuntu | 17.10 | noarch | libxfont1-dbgsym | < 1:1.5.2-4ubuntu1.1 | UNKNOWN |
Ubuntu | 17.10 | noarch | libxfont1-dev | < 1:1.5.2-4ubuntu1.1 | UNKNOWN |
Ubuntu | 17.10 | noarch | libxfont2 | < 1:2.0.1-3ubuntu1.1 | UNKNOWN |
Ubuntu | 17.10 | noarch | libxfont-dev | < 1:2.0.1-3ubuntu1.1 | UNKNOWN |
Ubuntu | 17.10 | noarch | libxfont2-dbgsym | < 1:2.0.1-3ubuntu1.1 | UNKNOWN |
Ubuntu | 17.10 | noarch | libxfont2-udeb | < 1:2.0.1-3ubuntu1.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libxfont1 | < 1:1.5.2-4ubuntu0.2 | UNKNOWN |
Ubuntu | 17.04 | noarch | libxfont1-dbgsym | < 1:1.5.2-4ubuntu0.2 | UNKNOWN |
Ubuntu | 17.04 | noarch | libxfont1-dev | < 1:1.5.2-4ubuntu0.2 | UNKNOWN |