lirantal daloradius 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.1$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in lirantal daloradius. Affected by this vulnerability is an unknown functionality. The manipulation leads to cookie httponly flag. This vulnerability is documented as CVE-2022-4630. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in lirantal daloradius (affected version not known) and classified as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a cookie httponly flag vulnerability. Using CWE to declare the problem leads to CWE-1004. The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag. Impacted is confidentiality. The summary by CVE is:

Sensitive Cookie Without 'HttpOnly' Flag in GitHub repository lirantal/daloradius prior to master.

The weakness was released 12/21/2022. It is possible to read the advisory at huntr.dev. The identification of this vulnerability is CVE-2022-4630 since 12/21/2022. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.

Upgrading eliminates this vulnerability. Applying the patch 6878619dc661b3009429777a1aeeb383ddc0166b 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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.3
CNA Vector (huntr.dev): 🔍

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Patch: 6878619dc661b3009429777a1aeeb383ddc0166b

Timelineinfo

12/21/2022 🔍
12/21/2022 +0 days 🔍
12/21/2022 +0 days 🔍
01/22/2023 +32 days 🔍

Sourcesinfo

Product: github.com

Advisory: 6878619dc661b3009429777a1aeeb383ddc0166b
Status: Confirmed

CVE: CVE-2022-4630 (🔍)
GCVE (CVE): GCVE-0-2022-4630
GCVE (VulDB): GCVE-100-216491

Entryinfo

Created: 12/21/2022 22:32
Updated: 01/22/2023 08:52
Changes: 12/21/2022 22:32 (48), 01/22/2023 08:52 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!