Security readout for executives and security teams
Plain-English summary
CVE-2023-6173 is a critical SQL injection vulnerability in TeoSOFT Software TeoBASE. Public CVE data says affected TeoBASE versions are through 27032024. A remote unauthenticated attacker may be able to access, change, or disrupt database-backed data. The vendor reportedly did not respond to disclosure, and no fix is identified in the provided sources.
Executive priority
Prioritize identification and containment of TeoBASE systems now. The technical severity is critical, and no patch is named in the provided sources. Business urgency depends on whether TeoBASE is used and exposed, but externally reachable instances should be treated as high-priority risk.
Technical view
The issue is CWE-89: improper neutralization of SQL special elements. CVSS 3.1 is 9.8: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. The provided record does not identify a vulnerable endpoint, proof of concept, patch version, or vendor advisory.
Likely exposure
Exposure is most relevant for organizations running TeoBASE, especially if reachable from untrusted networks. The sources do not provide deployment details, affected configurations, or internet exposure prevalence. Treat any TeoBASE instance through 27032024 as potentially affected until vendor or trusted national guidance confirms otherwise.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The vulnerability class and CVSS vector indicate plausible remote unauthenticated exploitation, but the sources do not include exploit details or evidence of attacks in the wild.
Researcher notes
Evidence is limited to CVE and Turkish government advisory references. The CVE record notes vendor non-response. The affected version statement is broad, and one affected entry lists version “0,” so rely on the description’s “through 27032024” wording and validate with authoritative follow-up guidance.
Mitigation direction
- Identify all TeoBASE deployments and their version or build date.
- Check TeoSOFT and national CERT guidance for updates or mitigations.
- Restrict TeoBASE access to trusted networks or VPN only.
- Apply database least-privilege controls for TeoBASE service accounts.
- Monitor TeoBASE and database logs for abnormal queries or access patterns.
Validation and detection
- Confirm whether TeoBASE is present in asset inventories.
- Verify whether any instance is versioned through 27032024.
- Determine whether TeoBASE is internet-accessible or externally reachable.
- Review compensating controls around network access and database permissions.
- Track vendor or government advisories for patch confirmation.
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-6173 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-24-0238CVE reference, TR-CERT · government-resource, broken-link
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-24-0238CVE 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.