Security readout for executives and security teams
Plain-English summary
Veribase has a critical SQL injection flaw that could let an unauthenticated remote attacker affect database confidentiality, integrity, and availability. The sources say Veribase is affected through 20231123 and note no vendor response. No source in the bundle names a fixed version.
Executive priority
Treat this as urgent if Veribase exists in the environment, especially if externally reachable. The vulnerability is critical and unauthenticated, but the source bundle does not prove active exploitation or identify a patch.
Technical view
CVE-2023-3377 is CWE-89 SQL injection in Veribilim Software Computer Veribase. The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction required. The bundle does not include vulnerable endpoints, proof details, or patch instructions.
Likely exposure
Exposure is likely limited to organizations running Veribase through 20231123. Internet-facing deployments should be prioritized first. The bundle provides no CPEs or reliable version inventory mapping, so validation depends on internal asset records and vendor confirmation.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source confirms active exploitation. Risk remains high because the CVSS vector indicates unauthenticated network exploitation with high confidentiality, integrity, and availability impact.
Researcher notes
The record has limited technical detail. The affected range is stated as through 20231123, while the structured affected data is sparse and lacks CPEs. Validate exposure through product inventory, deployment review, and official advisory tracking rather than endpoint assumptions.
Mitigation direction
- Identify any Veribase deployments and confirm versions with application owners.
- Check Veribilim and government advisory channels for fixed versions or vendor guidance.
- Restrict external access to Veribase until remediation status is clear.
- Review database account privileges used by Veribase and remove unnecessary permissions.
- Increase monitoring for unusual Veribase database errors, authentication anomalies, or data access patterns.
Validation and detection
- Search asset inventory for Veribase installations and owners.
- Confirm whether any deployment is versioned through 20231123.
- Determine whether Veribase is reachable from the internet or untrusted networks.
- Review vendor or government advisories for patch, workaround, or end-of-support status.
- Check security logs for suspicious SQL errors or abnormal database access tied to Veribase.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-3377 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
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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:U/C:H/I:H/A:H3.95.9TR-CERTVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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-23-0655CVE reference, TR-CERT · government-resource, broken-link
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-23-0655CVE 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.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.