Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
`mykey` implements MIKEY (RFC 3830) for SRTP key exchange. No receive path verified the MIKEY message authentication code. `crypto::verify_mac` existed and was correct, but it was called only from unit tests — neither `MikeyMessage::from_bytes` nor `MikeyMessage::complete_psk` invoked it. `new_psk_init` computed an HMAC-SHA-1-160 over the serialized message and appended it, so the tag was present on the wire and looked like integrity protection. It was decorative: a receiver accepted any message regardless of whether the MAC was correct, wrong, or absent. Consequences - An attacker able to inject or modify MIKEY messages in transit faced no integrity check. Modified RAND, SSRC or security-policy payloads were accepted silently. Note that this does not require a man-in-the-middle position: since nothing was checked, a wholly forged PSK-Init was accepted. - Pre-shared key mode therefore provided no mutual authentication, despite the documentation claiming that it did. Possession of…
Recommended action: Upgrade to 2.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
`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`…
Recommended action: Upgrade to 2.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.