LiveActive security incident?Get immediate response
CVE Record

CVE-2024-28326: Incorrect Access Control in ASUS RT-N12+ B1 and RT-N12 D1 routers allows local attackers to obtain root ter...

Incorrect Access Control in ASUS RT-N12+ B1 and RT-N12 D1 routers allows local attackers to obtain root terminal access via the the UART interface.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-28326 affects ASUS RT-N12+ B1 and RT-N12 D1 routers. A person with local physical access may obtain a root terminal through the UART interface. This is not a remote internet exploit based on the supplied sources, but it can fully compromise a device if someone can handle it.

Executive priority

Prioritize locations where these routers are physically reachable by untrusted people. The business risk is full device compromise, but the attack is constrained by physical access rather than broad remote exposure.

Technical view

The CVE describes incorrect access control mapped to CWE-1263. The CVSS 3.1 vector is AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, score 6.8. The issue requires physical access and can result in root terminal access through UART, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where named ASUS router models are deployed in locations with weak physical control, such as branch offices, shared facilities, labs, or customer-accessible spaces. The supplied CVE metadata lists affected CPE data as unavailable.

Exploitation context

The source bundle does not indicate known active exploitation, and KEV is false. Exploitation requires local physical access to the router hardware via UART, so attacker opportunity depends mainly on device placement and physical security.

Researcher notes

Evidence is limited to the CVE record and referenced public write-up. The CVE names UART-root access but does not provide a vendor patch, affected CPEs, or confirmed exploitation in the supplied bundle. Avoid assuming additional ASUS models are affected.

Mitigation direction

  • Inventory ASUS RT-N12+ B1 and RT-N12 D1 routers.
  • Check ASUS guidance for firmware, support status, or hardware remediation.
  • Restrict physical access to deployed routers and network closets.
  • Replace or retire exposed affected models if no vendor remediation exists.
  • Treat tampered or unattended devices as potentially compromised.

Validation and detection

  • Confirm model and hardware revision from device labels or asset records.
  • Identify affected units in public, shared, or remote-accessible locations.
  • Review vendor guidance for CVE-2024-28326 before testing.
  • Inspect devices for tampering if physical access was uncontrolled.
  • Review configuration integrity after any suspected physical access event.
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 · low confidence lookup

CWE-1263: 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
cve · low confidence lookup

CVE-2024-28326 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
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/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
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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
6.8CVSS 3.1MediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H0.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2024-28326Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:P/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
cvssV3_1other:ssvc
CVECVE Program Container
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-1263 · source CWE mapping

Improper Physical Access Control

Improper Physical Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.