What is the severity of CVE-2022-32282?

CVE-2022-32282 has been classified with a medium severity level due to the risk of unauthorized access to user accounts.

How does CVE-2022-32282 affect user accounts?

CVE-2022-32282 allows an attacker with a user's password hash to log in directly to their account, resulting in unauthorized access.

How do I fix CVE-2022-32282?

To mitigate CVE-2022-32282, ensure that password hashes are not directly usable for authentication by implementing proper security measures.

Is CVE-2022-32282 present in all versions of WWBN AVideo?

No, CVE-2022-32282 specifically affects WWBN AVideo version 11.6 and the development master commit 3f7c0364.

What can be done to secure accounts affected by CVE-2022-32282?

Users should update their passwords and review their account activity regularly to secure their accounts against CVE-2022-32282.

Vulnerability/
CVE-2022-32282

high

8.8

CWE

287 836

22/8/2022

16/9/2024

CVE-2022-32282

First published: Mon Aug 22 2022(Updated: )

An improper password check exists in the login functionality of WWBN AVideo 11.6 and dev master commit 3f7c0364. An attacker that owns a users' password hash will be able to use it to directly login into the account, leading to increased privileges.

Credit: talos-cna@cisco.com

Affected Software	Affected Version	How to fix
WWBN AVideo	=11.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-32282?
CVE-2022-32282 has been classified with a medium severity level due to the risk of unauthorized access to user accounts.
How does CVE-2022-32282 affect user accounts?
CVE-2022-32282 allows an attacker with a user's password hash to log in directly to their account, resulting in unauthorized access.
How do I fix CVE-2022-32282?
To mitigate CVE-2022-32282, ensure that password hashes are not directly usable for authentication by implementing proper security measures.
Is CVE-2022-32282 present in all versions of WWBN AVideo?
No, CVE-2022-32282 specifically affects WWBN AVideo version 11.6 and the development master commit 3f7c0364.
What can be done to secure accounts affected by CVE-2022-32282?
Users should update their passwords and review their account activity regularly to secure their accounts against CVE-2022-32282.

collector/nvd-index
agent/references
agent/weakness
agent/type
agent/softwarecombine
agent/severity
agent/author
agent/tags
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
vendor/wwbn
canonical/wwbn avideo
version/wwbn avideo/11.6

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-32282?
CVE-2022-32282 has been classified with a medium severity level due to the risk of unauthorized access to user accounts.
How does CVE-2022-32282 affect user accounts?
CVE-2022-32282 allows an attacker with a user's password hash to log in directly to their account, resulting in unauthorized access.
How do I fix CVE-2022-32282?
To mitigate CVE-2022-32282, ensure that password hashes are not directly usable for authentication by implementing proper security measures.
Is CVE-2022-32282 present in all versions of WWBN AVideo?
No, CVE-2022-32282 specifically affects WWBN AVideo version 11.6 and the development master commit 3f7c0364.
What can be done to secure accounts affected by CVE-2022-32282?
Users should update their passwords and review their account activity regularly to secure their accounts against CVE-2022-32282.