LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24149: TOTOLINK CA300-PoE V6.2c.884 was discovered to contain a hard code password for root which is stored in the...

TOTOLINK CA300-PoE V6.2c.884 was discovered to contain a hard code password for root which is stored in the component /etc/shadow.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A TOTOLINK CA300-PoE firmware version reportedly contains a hardcoded root password stored in its shadow password file. If an attacker can reach the affected device, the CVSS data indicates potential full compromise of confidentiality, integrity, and availability. No source in the bundle confirms active exploitation or a vendor patch.

Executive priority

Treat this as urgent for any deployed TOTOLINK CA300-PoE V6.2c.884 device. Prioritize discovery and exposure reduction first, then vendor-confirmed remediation or replacement. Business impact could include loss of network device control and downstream service disruption.

Technical view

CVE-2023-24149 is classified as CWE-798: use of hardcoded credentials. The CVE describes TOTOLINK CA300-PoE V6.2c.884 storing a root password in /etc/shadow. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is likely limited to environments running TOTOLINK CA300-PoE V6.2c.884, especially where device management is reachable from untrusted networks. The CVE record lacks CPE data and lists affected vendor/product as n/a, so confirmation requires manual asset and firmware review.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The risk is still serious because hardcoded root credentials can enable complete device compromise if reachable. Public technical details exist in the referenced GitHub write-up, but the evidence set is sparse.

Researcher notes

The public record identifies the issue and severity, but affected-product metadata is incomplete and no official fix is cited in the bundle. Validate against physical inventory, firmware banners, configuration records, and vendor advisories. Do not assume other TOTOLINK models are affected without separate evidence.

Mitigation direction

  • Check TOTOLINK guidance for fixed firmware, replacement advice, or official mitigations.
  • Remove affected device management interfaces from public or untrusted network access.
  • Restrict administration to trusted networks with firewall or management VLAN controls.
  • Consider replacing devices if no vendor-supported fix exists.
  • Monitor privileged access and configuration changes on affected devices.

Validation and detection

  • Inventory TOTOLINK CA300-PoE devices and record exact firmware versions.
  • Confirm whether any device runs V6.2c.884.
  • Verify management interfaces are not exposed to the internet or untrusted networks.
  • Review device logs for unexpected privileged access or configuration changes.
  • Track vendor advisories and CVE updates for confirmed fixes or affected-version changes.
Prepared
Confidence
medium
Sources
3

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

CWE-798: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-24149 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
0Timeline events
0ADP providers
2Source links

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.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-24149Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-798 · source CWE mapping

Use of Hard-coded Credentials

Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.