In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp process_sdp() declares union nf_inet_addr rtp_addr on the stack and passes it to the nf_nat_sip sdp_session hook after walking the SDP media descriptions. However rtp_addr is only initialized inside the media loop when a recognized media type with a non-zero port is found. If the SDP body contains no m= lines, only inactive media sections (m=audio 0 ...) or only unrecognized media types, rtp_addr is never assigned. Despite that, the function still calls hooks->sdp_session() with &rtp_addr, causing nf_nat_sdp_session() to format the stale stack value as an IP address and rewrite the SDP session owner and connection lines with it. With CONFIG_INIT_STACK_ALL_ZERO (default on most distributions) this results in the session-level o= and c= addresses being rewritten to 0.0.0.0 for inactive SDP sessions. Without stack auto-init the rewritten address is whatever happened to be on the stack. Fix this by pre-initializing rtp_addr from the session-level connection address (caddr) when available, and tracking via a have_rtp_addr flag whether any valid address was established. Skip the sdp_session hook entirely when no valid address exists.
| Vendor | Product | Versions |
|---|---|---|
| linux | linux kernel | 4ab9e64e5e3c0516577818804aaf13a630d67bc9, 4ab9e64e5e3c0516577818804aaf13a630d67bc9, 4ab9e64e5e3c0516577818804aaf13a630d67bc9, 4ab9e64e5e3c0516577818804aaf13a630d67bc9, 4ab9e64e5e3c0516577818804aaf13a630d67bc9, 4ab9e64e5e3c0516577818804aaf13a630d67bc9, 4ab9e64e5e3c0516577818804aaf13a630d67bc9, 4ab9e64e5e3c0516577818804aaf13a630d67bc9, 2.6.26 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| linux | linux | mitre_affected | 90% |
| open source | open source linux kernel | cert_advisory | 90% |
Updated severity to CRITICAL, added new affected versions, and corrected exploit availability.
Updated description with more technical detail, added affected version 2.6.26, changed severity to HIGH, added CWE-758, and marked exploit as available and actively exploited.
Initial creation