Bug 956145 (CVE-2013-3235) - CVE-2013-3235 Kernel: tipc: info leaks via msg_name in recv_msg/recv_stream
Summary: CVE-2013-3235 Kernel: tipc: info leaks via msg_name in recv_msg/recv_stream
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-3235
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 956148 956149
Blocks: 858947
TreeView+ depends on / blocked
 
Reported: 2013-04-24 10:48 UTC by Prasad J Pandit
Modified: 2021-02-17 07:46 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-09 17:50:43 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1034 0 normal SHIPPED_LIVE Low: kernel security and bug fix update 2013-07-10 07:51:23 UTC

Description Prasad J Pandit 2013-04-24 10:48:53 UTC
Linux kernel built with the The Transparent Inter Process Communication
(CONFIG_TIPC) protocol support is vulnerable to an information leakage flaw.
It occurs while receiving messages via recvmsg(2) socket call.

A user/program could use this flaw to leak kernel memory bytes.

Upstream fix:
-------------
 -> http://git.kernel.org/linus/60085c3d009b0df252547adb336d1ccca5ce52ec

Reference:
----------
 -> www.openwall.com/lists/oss-security/2013/04/14/3

Comment 1 Prasad J Pandit 2013-04-24 10:53:11 UTC
Statement:

This issue does not affect the versions of Linux kernel as shipped with
Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2.

This issue affects the version of the kernel package as shipped with
Red Hat Enterprise Linux 5. Future kernel updates for Red Hat Enterprise Linux 5
may address this issue.

Comment 3 errata-xmlrpc 2013-07-10 03:57:00 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2013:1034 https://rhn.redhat.com/errata/RHSA-2013-1034.html


Note You need to log in before you can comment on or make changes to this bug.