FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-12-18 19:03:49 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML ID	Description
2fe40238-480f-11e5-adde-14dae9d210b8	tarsnap -- buffer overflow and local DoS Colin Percival reports: 1. SECURITY FIX: When constructing paths of objects being archived, a buffer could overflow by one byte upon encountering 1024, 2048, 4096, etc. byte paths. Theoretically this could be exploited by an unprivileged user whose files are being archived; I do not believe it is exploitable in practice, but I am offering a $1000 bounty for the first person who can prove me wrong: http://www.daemonology.net/blog/2015-08-21-tarsnap-1000-exploit-bounty.html 2. SECURITY FIX: An attacker with a machine's write keys, or with read keys and control of the tarsnap service, could make tarsnap allocate a large amount of memory upon listing archives or reading an archive the attacker created; on 32-bit machines, tarsnap can be caused to crash under the aforementioned conditions. Discovery 2015-08-21 Entry 2015-08-21 tarsnap < 1.0.36 http://mail.tarsnap.com/tarsnap-announce/msg00032.html http://www.daemonology.net/blog/2015-08-21-tarsnap-1000-exploit-bounty.html

VuXML ID

Description

2fe40238-480f-11e5-adde-14dae9d210b8

tarsnap -- buffer overflow and local DoS

Colin Percival reports:

1. SECURITY FIX: When constructing paths of objects being archived, a buffer could overflow by one byte upon encountering 1024, 2048, 4096, etc. byte paths. Theoretically this could be exploited by an unprivileged user whose files are being archived; I do not believe it is exploitable in practice, but I am offering a $1000 bounty for the first person who can prove me wrong: http://www.daemonology.net/blog/2015-08-21-tarsnap-1000-exploit-bounty.html

2. SECURITY FIX: An attacker with a machine's write keys, or with read keys and control of the tarsnap service, could make tarsnap allocate a large amount of memory upon listing archives or reading an archive the attacker created; on 32-bit machines, tarsnap can be caused to crash under the aforementioned conditions.

Discovery 2015-08-21
Entry 2015-08-21
tarsnap

< 1.0.36

http://mail.tarsnap.com/tarsnap-announce/msg00032.html
http://www.daemonology.net/blog/2015-08-21-tarsnap-1000-exploit-bounty.html