CVE-2024-28328
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 · uneditedCSV Injection vulnerability in the Asus RT-N12+ router allows administrator users to inject arbitrary commands or formulas in the client name parameter which can be triggered and executed in a different user session upon exporting to CSV format.
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 confidenceCSV Injection in Asus RT-N12+ router allows admin users to inject malicious formulas (=, +, -, @ prefixes) into the client name parameter. When another user exports device/client data to CSV, the injected formulas are interpreted by spreadsheet software, potentially executing arbitrary commands in the victim's session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm router model is Asus RT-N12+Log into the router admin interface and check the Device Model or System Status page, or check the product label on the device itselfAffected if The router model is Asus RT-N12+ (any firmware version)
-
Verify admin access to routerLog into the router web interface at the default gateway IP (typically 192.168.1.1) using admin credentialsAffected if You have valid admin credentials and can access the router administration panel
-
Locate DHCP client or device listNavigate to the router's DHCP or Client List settings (usually under LAN or Network settings) where connected devices are displayedAffected if The router web interface exposes a list of DHCP clients or connected devices that can be viewed or exported
-
Check for CSV export functionalityLook for an Export, Download, or CSV button next to the client/device list - this is where injected formulas would be renderedAffected if The router interface provides an option to export device/client data to CSV or a spreadsheet-compatible format
-
Test client name injection capabilityIf you can add or edit a client reservation, attempt to set the client name to a formula prefix character (=, +, -, @)Affected if The router accepts formula prefix characters in the client name field without sanitization or rejection
-
Verify exported CSV interprets formulasExport the device list to CSV and open it in a spreadsheet application; check if formula prefixes are interpreted (cell shows formula behavior rather than literal text)Affected if The exported CSV file interprets characters like =, +, -, @ as formula initiators rather than plain text
You are affected if you use an Asus RT-N12+ router with admin access and the device list includes a CSV export feature that does not sanitize formula characters in client names.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataInput validation should be implemented to sanitize or reject formula characters (=, +, -, @, tab, CR) in client name fields; alternatively, CSV export should prefix formula characters with a single quote or apply output encoding to prevent formula interpretation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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