3 ms·
While the DoS of accounts-daemon is bad, it seems like the real problem here is that gdm3 running with broken/absent/etc. accounts-daemon will believe there are
by stormbrew 6y ago
While the DoS of accounts-daemon is bad, it seems like the real problem here is that gdm3 running with broken/absent/etc. accounts-daemon will believe there are no accounts even though there may be? Surely this is extremely trusting behaviour on gdm3's part and should also be fixed?
But all the updated versions are for accounts-version, not gdm3. Do they change the 'default' response somehow?
- sce 6y agoLooks like it's fixed upstream https://gitlab.gnome.org/GNOME/gdm/-/issues/642 https://gitlab.gnome.org/GNOME/gdm/-/issues/642
- stormbrew 6y agoAh, cool. That's good. CVE for that appears to be https://nvd.nist.gov/vuln/detail/CVE-2020-16125 https://nvd.nist.gov/vuln/detail/CVE-2020-16125 and fixed in 3.36.2 or 3.38.2..