Forgekeep nebula-mesh
nebula-mesh: Operator session tokens stored in plaintext in the database
nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version 0.3.8, Operator session tokens are stored in plaintext in the operator_sessions table (the token column is the PRIMARY KEY). The session token is a 32-byte random hex value sent directly in a cookie and valid for 24 hours. Anyone who can read the database (backup, snapshot, file copy, or SQL-level disclosure) obtains every active session token and can hijack operator sessions directly, with no further authentication. This issue has been patched in version 0.3.8.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-312
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
forgekeep nebula-mesh
- < 0.3.8
Fixed in 0.3.8
Mitigation
Upgrade nebula-mesh to 0.3.8 or later.
References
- Vendor advisory github.com/forgekeep/nebula-mesh/security/advi…
- Patch github.com/forgekeep/nebula-mesh/commit/7cb01b…
- Release notes github.com/forgekeep/nebula-mesh/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.