netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4ab9e64e5e3c0516577818804aaf13a630d67bc9 · fixed in faa6ea32797a1847790514ff0da1be1d09771580; From 4ab9e64e5e3c0516577818804aaf13a630d67bc9 · fixed in 82baeb871e8f04906bc886273fdf0209e1754eb3; From 4ab9e64e5e3c0516577818804aaf13a630d67bc9 · fixed in 6e5e3c87b7e6212f1d8414fc2e4d158b01e12025; From 4ab9e64e5e3c0516577818804aaf13a630d67bc9 · fixed in fe463e76c9b4b0b43b5ee8961b4c500231f1a3f6; From 4ab9e64e5e3c0516577818804aaf13a630d67bc9 · fixed in 7edca70751b9bdb5b83eed53cde21eccf3c86147; From 4ab9e64e5e3c0516577818804aaf13a630d67bc9 · fixed in 01f34a80ac23ae90b1909b94b4ed05343a62f646; From 4ab9e64e5e3c0516577818804aaf13a630d67bc9 · fixed in 52fdda318ef2362fc5936385bcb8b3d0328ee629; From 4ab9e64e5e3c0516577818804aaf13a630d67bc9 · fixed in 6a2b724460cb67caed500c508c2ae5cf012e4db4
- Linux Linux
2.6.26
- KernelLinux
From 2.6.26 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.168; From 6.2.0 · fixed in 6.6.131; From 6.7.0 · fixed in 6.12.80; From 6.13.0 · fixed in 6.18.21; From 6.19.0 · fixed in 6.19.11
References 8
git.kernel.org
- stable/c/faa6ea32797a1847790514ff0da1be1d09771580
- stable/c/82baeb871e8f04906bc886273fdf0209e1754eb3
- stable/c/6e5e3c87b7e6212f1d8414fc2e4d158b01e12025
- stable/c/fe463e76c9b4b0b43b5ee8961b4c500231f1a3f6
- stable/c/7edca70751b9bdb5b83eed53cde21eccf3c86147
- stable/c/01f34a80ac23ae90b1909b94b4ed05343a62f646
- stable/c/52fdda318ef2362fc5936385bcb8b3d0328ee629
- stable/c/6a2b724460cb67caed500c508c2ae5cf012e4db4