https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 23:30:36 +0000 https://cve.radiocsirt.org/vuln/bdu:2020-05642 bdu:2020-05642 https://cve.radiocsirt.org/vuln/bdu:2020-05642 https://cve.radiocsirt.org/vuln/euvd-2026-69567 EUVD-2026-69567 https://cve.radiocsirt.org/vuln/euvd-2026-69567 https://cve.radiocsirt.org/vuln/fkie_cve-2018-19046 <p>keepalived 2.0.8 didn&#39;t check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.</p> <p>keepalived 2.0.8 didn&#39;t check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2018-19046 https://cve.radiocsirt.org/vuln/ghsa-fjwx-29fr-83hw <p>keepalived 2.0.8 didn&#39;t check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.</p> <p>keepalived 2.0.8 didn&#39;t check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.</p> https://cve.radiocsirt.org/vuln/ghsa-fjwx-29fr-83hw https://cve.radiocsirt.org/vuln/gsd-2018-19046 gsd-2018-19046 https://cve.radiocsirt.org/vuln/gsd-2018-19046 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10893-1 <p>keepalived-2.2.2-4.2 on GA media</p> <p>keepalived-2.2.2-4.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10893-1 https://cve.radiocsirt.org/vuln/suse-su-2020:0779-1 <p>Security update for keepalived</p> <p>Security update for keepalived</p> https://cve.radiocsirt.org/vuln/suse-su-2020:0779-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-19046 <p><strong>Affected:</strong> Ubuntu:18.04:LTS: keepalived</p> <p>keepalived 2.0.8 didn&#39;t check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.</p> <p><strong>Affected:</strong> Ubuntu:18.04:LTS: keepalived</p> <p>keepalived 2.0.8 didn&#39;t check for existing plain files when writing data to a temporary file upon a call to PrintData or PrintStats. If a local attacker had previously created a file with the expected name (e.g., /tmp/keepalived.data or /tmp/keepalived.stats), with read access for the attacker and write access for the keepalived process, then this potentially leaked sensitive information.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-19046