aboutsummaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authordes <des@FreeBSD.org>2004-06-08 05:17:01 +0800
committerdes <des@FreeBSD.org>2004-06-08 05:17:01 +0800
commit4caab59b902fb9d066ad2a589e3e0048342fcec9 (patch)
tree61f9d78a8e28557cfb8e2a663afcf00bce66606b /security
parent31b213a38570f6478ffed485b9621ad01a49292f (diff)
downloadfreebsd-ports-gnome-4caab59b902fb9d066ad2a589e3e0048342fcec9.tar.gz
freebsd-ports-gnome-4caab59b902fb9d066ad2a589e3e0048342fcec9.tar.zst
freebsd-ports-gnome-4caab59b902fb9d066ad2a589e3e0048342fcec9.zip
Add FreeBSD-SA-04:12.jailroute.
Diffstat (limited to 'security')
-rw-r--r--security/vuxml/vuln.xml32
1 files changed, 32 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml
index 4a2a0b80d926..f75e2a57d3e0 100644
--- a/security/vuxml/vuln.xml
+++ b/security/vuxml/vuln.xml
@@ -30,6 +30,38 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+ <vuln vid="fb5e227e-b8c6-11d8-b88c-000d610a3b12">
+ <topic>jailed processes can manipulate host routing tables</topic>
+ <affects>
+ <system>
+ <name>FreeBSD</name>
+ <range><ge>4.9</ge><lt>4.9_10</lt></range>
+ <range><ge>4.0</ge><lt>4.8_23</lt></range>
+ </system>
+ </affects>
+ <description>
+ <body xmlns="http://www.w3.org/1999/xhtml">
+ <p>A programming error resulting in a failure to verify that
+ an attempt to manipulate routing tables originated from a
+ non-jailed process.</p>
+
+ <p>Jailed processes running with superuser privileges could
+ modify host routing tables. This could result in a variety
+ of consequences including packets being sent via an
+ incorrect network interface and packets being discarded
+ entirely.</p>
+ </body>
+ </description>
+ <references>
+ <cvename>CAN-2004-0125</cvename>
+ <freebsdsa>SA-04:12.jailroute</freebsdsa>
+ </references>
+ <dates>
+ <discovery>2004-02-03</discovery>
+ <entry>2004-06-07</entry>
+ </dates>
+ </vuln>
+
<vuln vid="1db1ed59-af07-11d8-acb9-000d610a3b12">
<topic>buffer cache invalidation implementation issues</topic>
<affects>