GHSA-fwjg-cm92-j3hj: Pre-shared key mode transmits the TGK in cleartext, exposing the SRTP master key
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: mykey (crates.io) 2.0.0.
Low priority for now. Upgrade to mykey (crates.io) 2.0.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
`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.
- Published
- Oct 9, 2026
- Updated
- Oct 12, 2026
- EPSS
- —
- CWE
- —
Report tools
Action score
36
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| crates.io | mykey | from 0.0.0-0 · before 2.0.0 | 2.0.0 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| crates.io:mykey | 2.0.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+13 d
- TodayNov 17, 2026+39 d
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.