Security readout for executives and security teams
Plain-English summary
The ATA-AOF mobile app reportedly embedded credentials and sent sensitive data without adequate protection. An unauthenticated remote attacker could abuse or bypass authentication. Business impact is concentrated on users and services tied to Ataturk University's ATA-AOF app before 20.06.2025.
Executive priority
Treat this as urgent for any organization relying on the ATA-AOF app. The critical rating reflects potential account and data compromise, but current public evidence does not show broad product exposure or confirmed exploitation.
Technical view
CVE-2025-4378 combines CWE-319 cleartext transmission and CWE-798 hard-coded credentials in Ataturk University's ATA-AOF Mobile Application. The CVSS 3.1 score is 10.0, with network attack vector, low complexity, no privileges, no user interaction, changed scope, and high confidentiality and integrity impact.
Likely exposure
Exposure appears limited to ATA-AOF Mobile Application deployments or users running versions before 20.06.2025. The bundle does not identify other Ataturk University products, backend components, operating systems, or third-party applications as affected.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and the supplied sources do not state active exploitation. The risk remains serious because the issue is remotely reachable, unauthenticated, low complexity, and can enable authentication abuse or bypass.
Researcher notes
The public record is sparse. One listed USOM reference is tagged as a broken link in the bundle. Analysis should stay anchored to the CVE record and the Turkish advisory, and avoid expanding affected scope beyond ATA-AOF Mobile Application before 20.06.2025.
Mitigation direction
- Check Ataturk University and Turkish government guidance for the fixed ATA-AOF app release.
- Move users off ATA-AOF Mobile Application versions before 20.06.2025.
- Invalidate or rotate any credentials embedded in affected mobile builds.
- Review authentication logs for abnormal ATA-AOF access patterns.
- Avoid assuming backend remediation is complete without vendor confirmation.
Validation and detection
- Inventory ATA-AOF Mobile Application versions used by students, staff, or managed devices.
- Confirm whether installed versions predate 20.06.2025.
- Verify vendor advisories for replacement build details and remediation status.
- Check whether affected credentials were present in deployed mobile packages.
- Review logs for authentication bypass or abuse indicators.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-319: 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 lookupCWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-4378 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L3.96TR-CERTVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.usom.gov.tr/bildirim/tr-25-0135CVE reference, TR-CERT · government-resource, broken-link
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-25-0135CVE reference, TR-CERT · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cleartext Transmission of Sensitive Information
Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.