LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6153: Authentication Bypass in TeoSOFT Software TeoBASE

Authentication Bypass by Primary Weakness vulnerability in TeoSOFT Software TeoBASE allows Authentication Bypass. This issue affects TeoBASE: through 20240327. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-6153 is a critical authentication-bypass flaw in TeoSOFT Software TeoBASE. The public CVE says an attacker can bypass authentication, with high potential impact to confidentiality, integrity, and availability. No active exploitation is cited in the provided sources.

Executive priority

Treat as urgent if TeoBASE is in use, especially if exposed to the internet or partner networks. Prioritize inventory, exposure reduction, and vendor guidance tracking because public data indicates critical impact but does not confirm a patch.

Technical view

The CVE describes CWE-305 authentication bypass affecting TeoBASE through 20240327. CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, and high CIA impact. The record notes the vendor did not respond to early disclosure.

Likely exposure

Organizations running TeoSOFT TeoBASE, especially versions through 20240327, should assume material exposure until they verify vendor status. The source data has limited affected-version detail and no CPEs, so asset confirmation may require software inventory and vendor records.

Exploitation context

There is no KEV listing and no cited source in the bundle confirming active exploitation. However, the CVSS vector indicates a remotely reachable, unauthenticated, low-complexity issue, which raises urgency for exposed deployments.

Researcher notes

Public details are sparse. The CVE asserts authentication bypass and high impact but provides no technical root cause, proof of concept, exploit status, or confirmed fix. One referenced USOM link is marked broken in the bundle; the alternate government advisory should be checked.

Mitigation direction

  • Identify all TeoBASE instances and owners.
  • Check TeoSOFT and cited government advisories for updated guidance.
  • If internet-exposed, consider isolating TeoBASE pending vendor guidance.
  • Apply any vendor-provided update or workaround when confirmed.
  • Increase monitoring for suspicious authentication or access anomalies.

Validation and detection

  • Confirm whether TeoBASE is deployed in production or remote-access environments.
  • Record installed TeoBASE version and compare against through-20240327 exposure statement.
  • Verify whether instances are reachable from untrusted networks.
  • Review authentication logs for unexpected successful access patterns.
  • Track CVE, CVE List, and government advisory updates.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-305: 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 lookup
description · low confidence lookup

Credential 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 lookup
cve · low confidence lookup

CVE-2023-6153 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-6153Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TeoSOFT SoftwareTeoBASE0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-305 · source CWE mapping

Authentication Bypass by Primary Weakness

Authentication Bypass by Primary Weakness represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.