CVE-2020-15909: High severity solarwinds vulnerability
SolarWinds N-central through 2020.1 allows session hijacking and requires user interaction or physical access. The N-Central JSESSIONID cookie attribute is not checked against multiple sources such as sourceip, MFA claim, etc. as long as the victim stays logged in within N-Central. To take advantage of this, cookie could be stolen and the JSESSIONID can be captured. On its own this is not a surprising result; low security tools allow the cookie to roam from machine to machine. The JSESSION cookie can then be used on the attackers’ workstation by browsing to the victim’s NCentral server URL and replacing the JSESSIONID attribute value by the captured value. Expected behavior would be to check this against a second source and enforce at least a reauthentication or multi factor request as N-Central is a highly privileged service.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2020-15909?
CVE-2020-15909 has been classified as a moderate severity vulnerability affecting SolarWinds N-central.
How do I fix CVE-2020-15909?
To mitigate CVE-2020-15909, ensure to implement proper session management practices, including monitoring session cookies and requiring multi-factor authentication.
What types of attacks does CVE-2020-15909 allow?
CVE-2020-15909 allows for session hijacking where an attacker can gain unauthorized access to a user's session.
What versions of SolarWinds N-central are affected by CVE-2020-15909?
CVE-2020-15909 affects all versions of SolarWinds N-central up to and including version 2020.1.
Is user interaction required to exploit CVE-2020-15909?
Yes, exploiting CVE-2020-15909 requires user interaction or physical access to the device.