dbcve.org
Gl Ar300m FirmwareOperating system · Gl Inet

CVE-2023-46454

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In GL.iNET GL-AR300M routers with firmware v4.3.7, it is possible to inject arbitrary shell commands through a crafted package name in the package information functionality.

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 confidence

The GL.iNET GL-AR300M router firmware v4.3.7 contains a command injection vulnerability in the package information functionality. Attackers can inject arbitrary shell commands by providing a specially crafted package name, likely due to improper input sanitization allowing shell metacharacters to be passed to system calls.

MitigationApply any vendor firmware updates when available. In the interim, disable the package information feature if possible and restrict network access to the router's administrative interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gl Ar300m FirmwareOperating system
Affected:= 4.3.7

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Access the router's web interface or check the device label to confirm the model is GL-AR300M
    Affected if The device is not a GL-AR300M router - this vulnerability affects only this specific model
  2. Check firmware version
    Navigate to the router's web administration panel, typically at 192.168.1.1, and locate the firmware version information in System > Firmware or Status section
    Affected if The installed firmware version is exactly 4.3.7 - this is the only version listed as affected in the provided advisory
  3. Verify package information feature accessibility
    Check if the package management or package information feature is accessible in the router's web interface, typically found under System > Software or Package section
    Affected if The package information feature is exposed and accessible to unauthenticated or low-privilege users - the vulnerability resides in this specific functionality
  4. Confirm network exposure
    Review router firewall settings and network accessibility to determine if the administrative interface is reachable from untrusted networks
    Affected if The router's web interface is exposed to WAN or untrusted networks - this would allow remote exploitation of the command injection flaw

A user is affected if they have a GL-AR300M router running firmware version 4.3.7 with the package information feature accessible, particularly if the admin interface is network-exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any vendor firmware updates when available. In the interim, disable the package information feature if possible and restrict network access to the router's administrative interface.

Recommended fix Moderate confidence

GL-AR300M firmware version newer than 4.3.7 (check vendor for latest stable release)

  1. 1. Visit the official GL.iNET support page at https://www.gl-inet.com/ for firmware downloads
  2. 2. Navigate to the GL-AR300M product page and check for the latest available firmware version
  3. 3. Download the most recent firmware version ( newer than v4.3.7 )
  4. 4. Access the GL-AR300M router web interface at http://192.168.1.1
  5. 5. Go to the Firmware Upgrade section in the administration panel
  6. 6. Upload the new firmware file and allow the upgrade process to complete
  7. 7. After reboot, verify the router is running the new firmware version
  8. 8. Test the package information functionality to confirm it no longer accepts command injection
Caveat Standard firmware upgrade - ensure to backup configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gl Ar300m Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46454 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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