justinas nosurf Token input validation

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.
6.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in justinas nosurf. This vulnerability affects unknown code of the component Token Handler. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2020-36564. No exploit is available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability classified as problematic has been found in justinas nosurf (affected version unknown). This affects an unknown functionality of the component Token Handler. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. The impact remains unknown. The summary by CVE is:

Due to improper validation of caller input, validation is silently disabled if the provided expected token is malformed, causing any user supplied token to be considered valid.

The weakness was published 12/28/2022. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-36564 since 07/29/2022. Neither technical details nor an exploit are publicly available.

Applying the patch 4d86df7a4affa1fa50ab39fb09aac56c3ce9c314 is able to eliminate this problem. The bugfix is ready for download at github.com.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Input validation
CWE: CWE-20
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: Patch
Status: 🔍

0-Day Time: 🔍

Patch: 4d86df7a4affa1fa50ab39fb09aac56c3ce9c314

Timelineinfo

07/29/2022 🔍
12/28/2022 +152 days 🔍
12/28/2022 +0 days 🔍
04/11/2025 +835 days 🔍

Sourcesinfo

Product: github.com

Advisory: 4d86df7a4affa1fa50ab39fb09aac56c3ce9c314
Status: Confirmed

CVE: CVE-2020-36564 (🔍)
GCVE (CVE): GCVE-0-2020-36564
GCVE (VulDB): GCVE-100-216945

Entryinfo

Created: 12/28/2022 09:39
Updated: 04/11/2025 19:34
Changes: 12/28/2022 09:39 (38), 01/25/2023 14:30 (1), 01/25/2023 14:32 (12), 04/11/2025 19:34 (16)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!