CVE-2024-3264Network attack vector

Unauthenticated signature spoofing via risky cryptography

Published Jun 24, 2024 · Updated Jun 3, 2026

Use of risky cryptography in MIA-MED before 1.0.14 allows remote attackers to spoof signatures and read protected information. The CNA record and its sole advisory do not identify the affected signature field, cryptographic algorithm, or validation operation. No privileges or user interaction are required, and the published impact is limited to disclosure of protected information.

CVSS severity5.3
Medium
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use of risky cryptography in MIA-MED before 1.0.14 allows remote attackers to spoof signatures and read protected information. The CNA record and its sole advisory do not identify the affected signature field, cryptographic algorithm, or validation operation. No privileges or user interaction are required, and the published impact is limited to disclosure of protected information.

The record

CVE
CVE-2024-3264
Published
Jun 24, 2024
Updated
Jun 3, 2026
Vendor
MİA Teknoloji A.Ş.
Product
MIA-MED
Classifications
CWE-327, CAPEC-475
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 24, 2024CVE publishedPublication date reported by the CVE source.
  2. Jun 3, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.0.14

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

MİA Teknoloji A.Ş. · MIA-MEDversion=0 <1.0.14

Published CVSS scores

5.3Computer Emergency Response Team of the Republic of TurkeyCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-327Use of a Broken or Risky Cryptographic Algorithm
CAPEC-475Signature Spoofing by Improper Validation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo