Security readout for executives and security teams
This CVE describes a SQL injection in Suprema BioStar 2 v2.8.16. A logged-in user could potentially extract sensitive database information through the absence-search API. The source data rates it medium, but confidentiality impact is high, which matters for identity and physical-access systems. Exposure appears limited to organizations running Suprema BioStar 2 v2.8.16. Risk is higher where BioStar 2 is reachable from broad internal networks, VPN users, or the internet. Structured CVE affected-product metadata is incomplete. Treat this as a near-term remediation item for any BioStar 2 deployment, especially where access-control or identity data is sensitive. It is not KEV-listed, but public disclosure and high confidentiality impact justify prompt validation. Mitigation focus: Identify whether Suprema BioStar 2 v2.8.16 is deployed.; Check Suprema guidance for a fixed version or official workaround.; Restrict BioStar 2 access to trusted administrative networks..
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-27167 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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:L/UI:N/S:U/C:H/I:N/A:N2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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://biostar2.ciklum.net/api/users/absence?search_month=1CVE reference, mitre
- https://www.linkedin.com/in/yuriy-tsarenko-a1453aa4/CVE reference, mitre
- https://protey.net/threads/cve-2023-27167-suprema-biostar-2-v2-8-16-sql-injection.995/CVE reference, mitre
- https://packetstormsecurity.com/files/171523/Suprema-BioStar-2-2.8.16-SQL-Injection.htmlCVE reference, mitre
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.