dbcve.org
Biostar 2Application · Supremainc

CVE-2023-33363

HIGH · 7.5 CVSS v3.1 Published 2023-08-03
Fix available
A fix is available. Upgrade to 2.9.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An authentication bypass vulnerability exists in Suprema BioStar 2 before 2.9.1, which allows unauthenticated users to access some functionality on BioStar 2 servers.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An authentication bypass vulnerability in the BioStar 2 web application server allows unauthenticated attackers to access certain server functionality without credentials. The flaw exists in versions prior to 2.9.1 and is exploitable remotely over the network.

MitigationUpgrade BioStar 2 to version 2.9.1 or later. Until patched, restrict network access to the BioStar 2 server from untrusted networks and monitor for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Biostar 2Application
Affected:< 2.9.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify BioStar 2 installation
    Check your systems for the presence of BioStar 2 application. Look for the BioStar 2 service or web application directory on your servers.
    Affected if BioStar 2 is installed on the system
  2. Determine installed BioStar 2 version
    Access the BioStar 2 web interface or check the application version information through the admin console or application logs. Compare your version against the affected range of versions prior to 2.9.1.
    Affected if The installed version is lower than 2.9.1
  3. Assess network exposure
    Determine if the BioStar 2 web server port (typically 443 or 8443) is accessible from untrusted networks. Use network scanning tools or review firewall rules to identify external accessibility.
    Affected if The BioStar 2 web interface is exposed to the internet or untrusted networks without proper access controls
  4. Review access logs for unauthorized requests
    Examine BioStar 2 server access logs for suspicious unauthenticated requests to administrative endpoints or API functions that would normally require authentication.
    Affected if Evidence of unauthenticated access attempts or successful unauthorized requests to protected functionality exists

You are affected if BioStar 2 version lower than 2.9.1 is installed and its web interface is network-accessible, allowing potential unauthenticated attackers to bypass authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.9.1 or later
Fixed in 2.9.1
Interim mitigation

Upgrade BioStar 2 to version 2.9.1 or later. Until patched, restrict network access to the BioStar 2 server from untrusted networks and monitor for unauthorized access attempts.

Recommended fix High confidence

2.9.1

  1. 1. Back up the current BioStar 2 configuration and database before upgrading.
  2. 2. Download BioStar 2 version 2.9.1 or later from the official Suprema support portal (kb.supremainc.com).
  3. 3. Stop the BioStar 2 server service.
  4. 4. Install or upgrade to BioStar 2 version 2.9.1 following the official installation documentation.
  5. 5. Start the BioStar 2 server service.
  6. 6. Verify that the authentication bypass vulnerability is remediated by confirming only authenticated users can access the BioStar 2 interface and API functionality.
Caveat Review release notes for any changes to existing integrations or workflows; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Biostar 2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-33363 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data