Mia Technology MİA-MED up to 1.0.6 wrong session

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

Summaryinfo

A vulnerability labeled as problematic has been found in Mia Technology MİA-MED up to 1.0.6. This affects an unknown part. The manipulation results in wrong session. This vulnerability is known as CVE-2023-6519. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Mia Technology MİA-MED up to 1.0.6. Affected is an unknown part. The manipulation with an unknown input leads to a wrong session vulnerability. CWE is classifying the issue as CWE-488. The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session. This is going to have an impact on confidentiality. CVE summarizes:

Exposure of Data Element to Wrong Session vulnerability in Mia Technology Inc. MİA-MED allows Read Sensitive Strings Within an Executable. This issue affects MİA-MED: before 1.0.7.

The weakness was published 02/08/2024 by Mustafa Anıl Yildirim. The advisory is shared for download at usom.gov.tr. This vulnerability is traded as CVE-2023-6519 since 12/05/2023. There are neither technical details nor an exploit publicly available.

Upgrading to version 1.0.7 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.3

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

CNA Base Score: 7.5
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Wrong session
CWE: CWE-488
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: MİA-MED 1.0.7

Timelineinfo

12/05/2023 🔍
02/08/2024 +65 days 🔍
02/08/2024 +0 days 🔍
05/20/2026 +832 days 🔍

Sourcesinfo

Advisory: usom.gov.tr
Researcher: Mustafa Anıl Yildirim
Status: Confirmed

CVE: CVE-2023-6519 (🔍)
GCVE (CVE): GCVE-0-2023-6519
GCVE (VulDB): GCVE-100-253200

Entryinfo

Created: 02/08/2024 14:04
Updated: 05/20/2026 17:43
Changes: 02/08/2024 14:04 (48), 05/20/2026 17:43 (17)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!