Security readout for executives and security teams
Plain-English summary
CVE-2024-28325 concerns an ASUS RT-N12+ B1 router issue where credentials may be stored in cleartext. A local attacker with some access could obtain those credentials and change router settings. The public metadata is limited, and the affected-product fields are incomplete.
Executive priority
Treat this as a moderate-priority network hygiene issue. It is not cited as actively exploited, but exposed or shared-access routers can become weak points for unauthorized network changes.
Technical view
The CVE describes cleartext credential storage mapped to CWE-256 and CWE-522. CVSS 3.1 is 6.1 with local attack vector, low complexity, low privileges, user interaction required, and high integrity impact. The reference naming appears inconsistent, so model validation matters.
Likely exposure
Exposure is most likely where the named ASUS router model is still deployed and accessible to local users or administrators. Business risk is higher in branch, small office, or unmanaged network environments where router configuration controls security boundaries.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation is local, requires low privileges and user interaction, and mainly enables unauthorized configuration changes after credential disclosure.
Researcher notes
Affected metadata lists vendor and product as n/a, while the description names ASUS RT-N12+ B1 and the reference URL mentions RT-N300-B1. Validate the exact device identity before scoping exposure or remediation.
Mitigation direction
Check ASUS guidance and firmware updates for the exact model before changing production devices.
Restrict router administration to trusted networks and authorized personnel only.
Rotate router administrative credentials after confirmed remediation or device replacement.
Replace unsupported affected devices if no vendor fix or safe workaround is available.
Validation and detection
Inventory environments for ASUS RT-N12+ B1 routers.
Verify model and firmware identifiers against CVE and vendor records.
Review router administration logs for unexpected configuration changes.
Document whether a vendor fix, workaround, or replacement path exists.
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-256: 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.
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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-256 · source CWE mapping
Plaintext Storage of a Password
Plaintext Storage of a Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.