LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6517: Seeing the SMS Verification Code in Mia Technology's Mia-Med

Exposure of Sensitive Information Due to Incompatible Policies vulnerability in Mia Technology Inc. MİA-MED allows Collect Data as Provided by Users. This issue affects MİA-MED: before 1.0.7.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-6517 concerns Mia Technology’s MİA-MED exposing sensitive information, specifically SMS verification codes. The CVE says versions before 1.0.7 are affected. For healthcare or patient-service workflows, exposed verification codes can undermine account verification and privacy controls.

Executive priority

Treat as high priority where MİA-MED supports patient, identity, or appointment workflows. The main business risk is unauthorized visibility of verification codes and related privacy exposure. Prioritize inventory, version confirmation, and upgrade planning.

Technical view

The issue is classified as CWE-213: Exposure of Sensitive Information Due to Incompatible Policies. CVSS 3.1 is 7.5: network-accessible, low complexity, no privileges, no user interaction, with high confidentiality impact only. The record states MİA-MED before 1.0.7 is affected.

Likely exposure

Exposure appears limited to organizations running Mia Technology MİA-MED before 1.0.7. The CVE metadata is inconsistent: the description names pre-1.0.7, while the affected version entry is sparse. Confirm installed versions directly.

Exploitation context

No cited source indicates active exploitation, and this CVE is not listed as KEV in the provided data. The CVSS vector indicates remote unauthenticated exposure may be possible, but public exploit details are not provided in the sources.

Researcher notes

Sources provide limited technical detail beyond CWE, CVSS, and affected version range. Avoid assuming root cause or exploitability beyond the CVSS vector. The USOM reference is marked broken in the bundle; the siberguvenlik.gov.tr advisory should be checked for current details.

Mitigation direction

  • Identify all MİA-MED deployments and their installed versions.
  • Upgrade to MİA-MED 1.0.7 or later if confirmed by vendor guidance.
  • Review Turkish government advisory TR-24-0087 for vendor-specific instructions.
  • Limit external access to MİA-MED until exposure is confirmed resolved.
  • Check logs and workflows for unintended SMS code disclosure.

Validation and detection

  • Confirm whether any MİA-MED instance is below version 1.0.7.
  • Review application responses and screens for SMS verification code exposure.
  • Verify no SMS codes are stored in accessible logs or reports.
  • Document compensating controls if upgrade timing is delayed.
  • Track vendor or government advisory updates for clarification.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-213: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-6517 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-6517Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Mia Technology Inc.MİA-MED0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.