WWBN AVideo Authentication Failure Vulnerability: Early Warning
- Severity
- CRITICAL
- CVSS
- 9.8
- Affected component
- wwbn-avideo (npm)
- Affected versions
- >= 29.0, <= 29.0 or >= 26.0, <= 26.0 or >= 25.0, <= 25.0 or >= 24.0, <= 24.0 or >= 22.0, <= 22.0 or >= 21.0, <= 21.0 or >= 18.0, <= 18.0 or >= 14.3.1, <= 14.3.1 or >= 14.3, <= 14.3 or >= 12.4, <= 12.4 or >= 11.6, <= 11.6 or >= 11.5, <= 11.5 or >= 11.1.1, <= 11.1.1 or >= 11.1, <= 11.1 or >= 11, <= 11 or >= 10.8, <= 10.8 or >= 8.9.1, <= 8.9.1 or >= 8.9, <= 8.9 or >= 8.7, <= 8.7 or >= 8.6, <= 8.6 or >= 8.5, <= 8.5 or >= 8.1, <= 8.1 or >= 7.8, <= 7.8 or >= 7.7, <= 7.7 or >= 7.6, <= 7.6 or >= 7.4, <= 7.4 or >= 7.3, <= 7.3 or >= 7.2, <= 7.2 or >= 4.0, <= 4.0 or >= 3.4, <= 3.4 or >= 2.7, <= 2.7 or >= 2.2, <= 2.2
- Patched version
- Not yet available
An authentication failure vulnerability has been reported in WWBN AVideo where the video_id_hash credential can be used to gain full administrator access indefinitely. This affects multiple versions of the wwbn-avideo npm package.
What happened
An early warning has been issued for a critical vulnerability in WWBN AVideo. The issue lies in the video_id_hash credential, which is a non-expiring, non-revocable bearer token. This token grants full administrator session access to the video owner's account. Attackers who obtain a video_id_hash can replay it indefinitely to authenticate as the video owner with full privileges, even after the owner changes their password.
The affected versions of the wwbn-avideo npm package are extensive, ranging from version 29.0 down to version 2.2. Engineers using this package should review their dependencies to determine if they are using an affected version.
What to do about it
- Monitor for any signs of exploitation in your systems.
- Consider restricting access to the affected component until a patch is available.
- Review your dependencies to identify if you are using an affected version of the wwbn-avideo npm package.
- No official fix has been published yet. Monitor the sources below for updates.
How 0Day would have caught this
wwbn-avideo is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
You are affected if you are using the wwbn-avideo npm package in versions >= 29.0, <= 29.0 or >= 26.0, <= 26.0 or >= 25.0, <= 25.0 or >= 24.0, <= 24.0 or >= 22.0, <= 22.0 or >= 21.0, <= 21.0 or >= 18.0, <= 18.0 or >= 14.3.1, <= 14.3.1 or >= 14.3, <= 14.3 or >= 12.4, <= 12.4 or >= 11.6, <= 11.6 or >= 11.5, <= 11.5 or >= 11.1.1, <= 11.1.1 or >= 11.1, <= 11.1 or >= 11, <= 11 or >= 10.8, <= 10.8 or >= 8.9.1, <= 8.9.1 or >= 8.9, <= 8.9 or >= 8.7, <= 8.7 or >= 8.6, <= 8.6 or >= 8.5, <= 8.5 or >= 8.1, <= 8.1 or >= 7.8, <= 7.8 or >= 7.7, <= 7.7 or >= 7.6, <= 7.6 or >= 7.4, <= 7.4 or >= 7.3, <= 7.3 or >= 7.2, <= 7.2 or >= 4.0, <= 4.0 or >= 3.4, <= 3.4 or >= 2.7, <= 2.7 or >= 2.2, <= 2.2.
What should I do right now?
Monitor for any signs of exploitation and consider restricting access to the affected component until a patch is available.
Is there a patch available?
No official fix has been published yet. Monitor the sources for updates.