Versa VOS session cookie forgery in ZTP web service
Versa VOS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Versa VOS |
|
|
Versa VOS
| Product | Affected | Fixed in |
|---|---|---|
| Versa VOS |
|
|
23.1.2 Aug-3-2026-HotfixThe Node.js web service on VOS (previously Versa FlexVNF) is used for URL-based Zero Touch Provisioning (ZTP) of the VOS appliance and is not required after provisioning is complete. The express-session middleware in server.js is configured with a hardcoded secret that is identical across all VOS appliances and is used to sign session cookies. An attacker who obtains a valid session ID from any source can compute the correct HMAC-SHA256 signature and forge a session cookie that the server accepts as legitimate. Because the secret is shared across all VOS appliances, a forged cookie is accepted by any VOS appliance in the deployment.
Versa’s security hardening guide for Hubs, Branches, and Controllers recommends disabling the Node.js web service after the initial provisioning of the VOS device. This vulnerability is not exploitable on VOS devices where the Node.js web service has been disabled.
From the CVE record · hackerone
The Node.js web service used for Zero Touch Provisioning on VOS uses the same hardcoded secret to sign session cookies across appliances. An attacker who obtains a valid session ID can forge a cookie accepted by any VOS appliance in the deployment where the service is enabled. The vulnerability is not exploitable on devices where the service has been disabled.
Operators of Versa VOS appliances with the Node.js web service enabled should check their devices; affected versions were not specified.