noVNC up to 0.4 Secure Flag Cookie cryptographic issue

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.2$0-$5k0.85

Summaryinfo

A vulnerability marked as critical has been reported in noVNC up to 0.4. Affected by this issue is some unknown functionality of the component Secure Flag Handler. Performing a manipulation results in cryptographic issue (Cookie). This vulnerability is reported as CVE-2013-7436. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in noVNC up to 0.4. This affects an unknown code of the component Secure Flag Handler. The manipulation with an unknown input leads to a cryptographic issue vulnerability (Cookie). CWE is classifying the issue as CWE-310. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:

noVNC before 0.5 does not set the secure flag for a cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.

The weakness was disclosed 04/10/2015 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2013-7436 since 03/12/2015. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.

Upgrading to version 0.5 eliminates this vulnerability.

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

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Name: Cookie
Class: Cryptographic issue / Cookie
CWE: CWE-310
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: noVNC 0.5
Patch: github.com

Timelineinfo

03/12/2015 🔍
04/10/2015 +29 days 🔍
04/10/2015 +0 days 🔍
04/11/2015 +1 days 🔍
05/03/2022 +2579 days 🔍

Sourcesinfo

Advisory: ad941faddead705cd611921730054767a0b32dcd
Status: Not defined
Confirmation: 🔍

CVE: CVE-2013-7436 (🔍)
GCVE (CVE): GCVE-0-2013-7436
GCVE (VulDB): GCVE-100-74757

Entryinfo

Created: 04/12/2015 01:10
Updated: 05/03/2022 14:42
Changes: 04/12/2015 01:10 (44), 05/06/2018 11:26 (6), 05/03/2022 14:39 (4), 05/03/2022 14:42 (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.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!