VDB-238933 · CVE-2023-40918 · Issue 1128

KnowStreaming 3.3.0 privileges management

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.
7.1	$0-$5k	0.00

Summaryinfo

A vulnerability identified as critical has been detected in KnowStreaming 3.3.0. This affects an unknown part. This manipulation causes an unknown weakness. This vulnerability appears as CVE-2023-40918. There is no available exploit.

Detailsinfo

A vulnerability classified as critical was found in KnowStreaming 3.3.0. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

KnowStreaming 3.3.0 is vulnerable to Escalation of Privileges. Unauthorized users can create a new user with an admin role.

The weakness was presented 09/06/2023 as 1128. The advisory is shared at github.com. This vulnerability is known as CVE-2023-40918 since 08/22/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-45457). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

KnowStreaming

Version

3.3.0

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.1
VulDB Meta Temp Score: 7.1

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

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

Exploitinginfo

Class: Privileges management
CWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/22/2023 🔍
09/06/2023 +15 days 🔍
09/06/2023 +0 days 🔍
01/30/2026 +877 days 🔍

Sourcesinfo

Advisory: 1128
Status: Confirmed

CVE: CVE-2023-40918 (🔍)
GCVE (CVE): GCVE-0-2023-40918
GCVE (VulDB): GCVE-100-238933
EUVD: 🔍

Entryinfo

Created: 09/06/2023 10:13
Updated: 01/30/2026 10:48
Changes: 09/06/2023 10:13 (35), 10/01/2023 14:42 (12), 01/30/2026 10:48 (16)
Complete: 🔍
Cache ID: 216::103

Submitinfo

Duplicate

Submit #XXXXXX: Xxxx Xxxxxxxxxxxxx X.x.x Xxxxxxxxxx Xx Xxxxxxxxxx (by gaogaostone)

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