Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 275/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 12:38 UTC Customize Public modeDiscuss ChangeIntel on Discord

Pre-shared key mode transmits the TGK in cleartext, exposing the SRTP master key

Exact source revision recorded 24 Oct 2026 13:19:54 UTC. It does not establish the source's current position. Latest evidence.

osv · RUSTSEC-2026-0335

Published

`mykey` implements MIKEY (RFC 3830) for SRTP key exchange. Pre-shared key mode transmitted the TEK Generation Key (TGK) in the clear. `MikeyMessage::new_psk_init` built its KEMAC payload with `EncAlg::Null` and placed the TGK in `enc_data` verbatim. Anyone able to read a PSK-Init message therefore recovers the TGK — and so the SRTP master key — **without knowing the pre-shared key**. The transmitted value was never even used by the receiver: `complete_psk` re-derived the TGK from the pre-shared key and ignored `enc_data` entirely. The field was write-only; it provided nothing and disclosed everything. A second consequence: the message authentication key was derived from the TGK rather than from the pre-shared key, so an attacker who read the TGK off the wire could also forge a valid message MAC. Integrity was lost along with confidentiality. That aspect is tracked separately as GHSA-xq78-wvcv-hqvj. ## Exploitability A MIKEY message is normally distributed as an SDP `a=key-mgmt:mikey` attribute, which in AES67 and SMPTE ST 2110 deployments is typically announced over SAP multicast. A passive listener on the media network recovers the session key with no active attack and no credentials. RFC 3830 §4.2.3 permits NULL encryption only where "the underlying protocols can guarantee security", and warns to use it with caution. An SDP file or a SAP announcement is not such a channel. ## The fix Pre-shared key mode now follows RFC 3830 §3.1 as key *transport*: the initiator generates a random TGK, frames it as a Key data sub-payload (§6.13), and encrypts it with AES-CM (§4.2.3) under an encryption key and 112-bit salt derived from the pre-shared key (§4.1.4). The message MAC is keyed from the pre-shared key and verified before anything is decrypted. This changes the wire format, so both ends of an exchange must be upgraded together. The incompatibility is silent: an old peer and a new peer complete the exchange without error and then derive different SRTP keys. ## Workarounds Use ephemeral Diffie-Hellman mode instead of pre-shared key mode, or carry the PSK-Init only over a channel that is already confidential and authenticated end to end.

Source published
9 Oct 2026 12:00:00 UTC
Source modified
12 Oct 2026 09:15:02 UTC
Observed here
24 Oct 2026 13:19:54 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 10 Nov 12:38 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current