Pterodactyl up to 1.6.2 cross-site request forgery

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.2$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in Pterodactyl up to 1.6.2. This vulnerability affects unknown code. Executing a manipulation can lead to cross-site request forgery. This vulnerability is handled as CVE-2021-41176. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in Pterodactyl up to 1.6.2 and classified as problematic. This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity.

The weakness was released 10/26/2021 as GHSA-m49f-hcxp-6hm6. The advisory is available at github.com. This vulnerability was named CVE-2021-41176 since 09/15/2021. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.

Upgrading to version 1.6.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 45999ba4ee1b2dcb12b4a2fa2cedfb6b5d66fac2 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 4.3
CNA Vector (GitHub, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Pterodactyl 1.6.3
Patch: 45999ba4ee1b2dcb12b4a2fa2cedfb6b5d66fac2

Timelineinfo

09/15/2021 🔍
10/26/2021 +41 days 🔍
10/26/2021 +0 days 🔍
10/30/2021 +4 days 🔍

Sourcesinfo

Advisory: GHSA-m49f-hcxp-6hm6
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-41176 (🔍)
GCVE (CVE): GCVE-0-2021-41176
GCVE (VulDB): GCVE-100-185386

Entryinfo

Created: 10/26/2021 12:55
Updated: 10/30/2021 11:47
Changes: 10/26/2021 12:55 (51), 10/30/2021 11:32 (2), 10/30/2021 11:39 (7), 10/30/2021 11:47 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!