{"answers":{"affected":"1 open source package ship an affected version, including mykey.","exploited":"There is no known exploitation of RUSTSEC-2026-0335 in the wild and no public exploit code.","fix":"Upgrade mykey to 2.0.0 or later.","what":"RUSTSEC-2026-0335 is a vulnerability in mykey, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0335 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0335 is a vulnerability in mykey, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2026-0335 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mykey (crates.io): affected from 0.0.0-0; fixed in 2.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0335/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0335/index.md)","id":"RUSTSEC-2026-0335","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0335/index.md","name":"RUSTSEC-2026-0335","record":{"aliases":["GHSA-fwjg-cm92-j3hj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust MIKEY library","requires_auth":"none","summary":"Passive network listeners can recover SRTP master keys from cleartext MIKEY messages, compromising media session confidentiality and integrity.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`mykey` implements MIKEY (RFC 3830) for SRTP key exchange. Pre-shared key mode\ntransmitted the TEK Generation Key (TGK) in the clear.\n\n`MikeyMessage::new_psk_init` built its KEMAC payload with `EncAlg::Null` and\nplaced the TGK in `enc_data` verbatim. Anyone able to read a PSK-Init message\ntherefore recovers the TGK — and so the SRTP master key — **without knowing the\npre-shared key**.\n\nThe transmitted value was never even used by the receiver: `complete_psk`\nre-derived the TGK from the pre-shared key and ignored `enc_data` entirely. The\nfield was write-only; it provided nothing and disclosed everything.\n\nA second consequence: the message authentication key was derived from the TGK\nrather than from the pre-shared key, so an attacker who read the TGK off the wire\ncould also forge a valid message MAC. Integrity was lost along with\nconfidentiality. That aspect is tracked separately as GHSA-xq78-wvcv-hqvj.\n\n## Exploitability\n\nA MIKEY message is normally distributed as an SDP `a=key-mgmt:mikey` attribute,\nwhich in AES67 and SMPTE ST 2110 deployments is typically announced over SAP\nmulticast. A passive listener on the media network recovers the session key with\nno active attack and no credentials.\n\nRFC 3830 §4.2.3 permits NULL encryption only where \"the underlying protocols can\nguarantee security\", and warns to use it with caution. An SDP file or a SAP\nannouncement is not such a channel.\n\n## The fix\n\nPre-shared key mode now follows RFC 3830 §3.1 as key *transport*: the initiator\ngenerates a random TGK, frames it as a Key data sub-payload (§6.13), and encrypts\nit with AES-CM (§4.2.3) under an encryption key and 112-bit salt derived from the\npre-shared key (§4.1.4). The message MAC is keyed from the pre-shared key and\nverified before anything is decrypted.\n\nThis changes the wire format, so both ends of an exchange must be upgraded\ntogether. The incompatibility is silent: an old peer and a new peer complete the\nexchange without error and then derive different SRTP keys.\n\n## Workarounds\n\nUse ephemeral Diffie-Hellman mode instead of pre-shared key mode, or carry the\nPSK-Init only over a channel that is already confidential and authenticated end\nto end.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Pre-shared key mode transmits the TGK in cleartext, exposing the SRTP master key","id":"RUSTSEC-2026-0335","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["2.0.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"mykey","purl":"pkg:cargo/mykey","source":"RUSTSEC-2026-0335"}],"products":null,"published":"2026-10-09","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Passive network listeners can recover SRTP master keys from cleartext MIKEY messages, compromising media session confidentiality and integrity.","url":"https://insights.sbomify.com/RUSTSEC-2026-0335/"}