What is the severity of CVE-2020-25621?

CVE-2020-25621 has been classified as a critical vulnerability due to its potential for unauthorized access to sensitive information.

How do I fix CVE-2020-25621?

To fix CVE-2020-25621, you should update SolarWinds N-Central to a version that requires authentication for the local database access.

What are the potential risks of CVE-2020-25621?

The risks of CVE-2020-25621 include unauthorized access to the database containing keys and passwords, which could lead to further exploitation.

Who is affected by CVE-2020-25621?

CVE-2020-25621 affects users of SolarWinds N-Central version 12.3.0.670.

Is there a workaround for CVE-2020-25621?

There are no known workarounds for CVE-2020-25621; the best approach is to apply security updates as they are released.

Vulnerability/
CVE-2020-25621

high

8.4

CWE

306

16/12/2020

4/8/2024

CVE-2020-25621

First published: Wed Dec 16 2020(Updated: )

An issue was discovered in SolarWinds N-Central 12.3.0.670. The local database does not require authentication: security is only based on ability to access a network interface. The database has keys and passwords.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
SolarWinds N-Central	=12.3.0.670

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-25621?
CVE-2020-25621 has been classified as a critical vulnerability due to its potential for unauthorized access to sensitive information.
How do I fix CVE-2020-25621?
To fix CVE-2020-25621, you should update SolarWinds N-Central to a version that requires authentication for the local database access.
What are the potential risks of CVE-2020-25621?
The risks of CVE-2020-25621 include unauthorized access to the database containing keys and passwords, which could lead to further exploitation.
Who is affected by CVE-2020-25621?
CVE-2020-25621 affects users of SolarWinds N-Central version 12.3.0.670.
Is there a workaround for CVE-2020-25621?
There are no known workarounds for CVE-2020-25621; the best approach is to apply security updates as they are released.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/weakness
agent/author
agent/last-modified-date
agent/description
agent/tags
agent/first-publish-date
agent/event
agent/source
vendor/solarwinds
canonical/solarwinds n-central
version/solarwinds n-central/12.3.0.670

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-2020-25621?
CVE-2020-25621 has been classified as a critical vulnerability due to its potential for unauthorized access to sensitive information.
How do I fix CVE-2020-25621?
To fix CVE-2020-25621, you should update SolarWinds N-Central to a version that requires authentication for the local database access.
What are the potential risks of CVE-2020-25621?
The risks of CVE-2020-25621 include unauthorized access to the database containing keys and passwords, which could lead to further exploitation.
Who is affected by CVE-2020-25621?
CVE-2020-25621 affects users of SolarWinds N-Central version 12.3.0.670.
Is there a workaround for CVE-2020-25621?
There are no known workarounds for CVE-2020-25621; the best approach is to apply security updates as they are released.