nsupdate.info CSRF Cookie base.py CSRF_COOKIE_HTTPONLY cookie httponly flag

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 was found in nsupdate.info. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the file src/nsupdate/settings/base.py of the component CSRF Cookie Handler. Performing a manipulation of the argument CSRF_COOKIE_HTTPONLY results in cookie httponly flag. This vulnerability is cataloged as CVE-2019-25091. It is possible to initiate the attack remotely. There is no exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as problematic has been found in nsupdate.info (version unknown). This affects an unknown function of the file src/nsupdate/settings/base.py of the component CSRF Cookie Handler. The manipulation of the argument CSRF_COOKIE_HTTPONLY with an unknown input leads to a cookie httponly flag vulnerability. CWE is classifying the issue as CWE-1004. The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag. This is going to have an impact on confidentiality.

The weakness was shared 12/27/2022 as 410. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2019-25091. Technical details are known, but no exploit is available.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CNA Base Score: 3.7
CNA Vector (VulDB): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Cookie httponly flag
CWE: CWE-1004 / CWE-732 / CWE-275
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: 60a3fe559c453bc36b0ec3e5dd39c1303640a59a

Timelineinfo

12/27/2022 🔍
12/27/2022 +0 days 🔍
12/27/2022 +0 days 🔍
01/25/2023 +29 days 🔍

Sourcesinfo

Advisory: 410
Status: Confirmed

CVE: CVE-2019-25091 (🔍)
GCVE (CVE): GCVE-0-2019-25091
GCVE (VulDB): GCVE-100-216909

Entryinfo

Created: 12/27/2022 23:47
Updated: 01/25/2023 09:33
Changes: 12/27/2022 23:47 (41), 01/25/2023 09:25 (2), 01/25/2023 09:29 (21), 01/25/2023 09:33 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!