CVE-2021-3169
First published: Fri Jul 23 2021(Updated: )
An issue in Jumpserver 2.6.2 and below allows attackers to create a connection token through an API which does not have access control and use it to access sensitive assets.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jumpserver | >=2.4.0<2.4.5 | |
| Jumpserver | >=2.5.0<2.5.4 | |
| Jumpserver | >=2.6.0<2.6.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-3169?
CVE-2021-3169 is classified as a high-severity vulnerability due to the potential for unauthorized access to sensitive assets.
How do I fix CVE-2021-3169?
To fix CVE-2021-3169, update Jumpserver to a version later than 2.6.2.
What is the impact of CVE-2021-3169?
The impact of CVE-2021-3169 includes the ability for attackers to create unauthorized connection tokens and access sensitive information.
Which versions of Jumpserver are affected by CVE-2021-3169?
Jumpserver versions 2.6.2 and below are affected by CVE-2021-3169.
What is the exploit vector for CVE-2021-3169?
The exploit vector for CVE-2021-3169 involves making API calls that lack proper access control.
- agent/type
- agent/references
- agent/severity
- agent/first-publish-date
- agent/weakness
- agent/event
- agent/description
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/jumpserver
- canonical/jumpserver
- version/jumpserver/2.4.0
- version/jumpserver/2.5.0
- version/jumpserver/2.6.0