FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The last vuln.xml file processed by FreshPorts is:

Revision:  446661
Date:      2017-07-26
Time:      15:06:28Z
Committer: mm

List all Vulnerabilities, by package

List all Vulnerabilities, by date

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

VuXML IDDescription
e3244a7b-5603-11e3-878d-20cf30e32f6dsubversion -- multiple vulnerabilities

Subversion Project reports:

mod_dontdothat does not restrict requests from serf based clients

mod_dontdothat allows you to block update REPORT requests against certain paths in the repository. It expects the paths in the REPORT request to be absolute URLs. Serf based clients send relative URLs instead of absolute URLs in many cases. As a result these clients are not blocked as configured by mod_dontdothat.

mod_dav_svn assertion triggered by non-canonical URLs in autoversioning commits

When SVNAutoversioning is enabled via SVNAutoversioning on commits can be made by single HTTP requests such as MKCOL and PUT. If Subversion is built with assertions enabled any such requests that have non-canonical URLs, such as URLs with a trailing /, may trigger an assert. An assert will cause the Apache process to abort.

Discovery 2013-11-15
Entry 2013-11-25
ge 1.4.0 lt 1.7.14

ge 1.8.0 lt 1.8.5

2ae24334-f2e6-11e2-8346-001e8c75030dsubversion -- remotely triggerable "Assertion failed" DoS vulnerability or read overflow.

Subversion Project reports:

Subversion's mod_dav_svn Apache HTTPD server module will trigger an assertion on some requests made against a revision root. This can lead to a DoS. If assertions are disabled it will trigger a read overflow which may cause a SEGFAULT (or equivalent) or undefined behavior.

Commit access is required to exploit this.

Discovery 2013-07-19
Entry 2013-07-24
Modified 2013-07-25
ge 1.8.0 lt 1.8.1

ge 1.7.0 lt 1.7.11

f8a913cc-1322-11e3-8ffa-20cf30e32f6dsvnserve is vulnerable to a local privilege escalation vulnerability via symlink attack.

Subversion Project reports:

svnserve takes a --pid-file option which creates a file containing the process id it is running as. It does not take steps to ensure that the file it has been directed at is not a symlink. If the pid file is in a directory writeable by unprivileged users, the destination could be replaced by a symlink allowing for privilege escalation. svnserve does not create a pid file by default.

All versions are only vulnerable when the --pid-file=ARG option is used.

Discovery 2013-08-30
Entry 2013-09-02
ge 1.4.0 lt 1.6.23_2

ge 1.7.0 lt 1.7.13

ge 1.8.0 lt 1.8.3