CVE-2023-47463
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 · uneditedInsecure Permissions vulnerability in GL.iNet AX1800 version 4.0.0 before 4.5.0 allows a remote attacker to execute arbitrary code via a crafted script to the gl_nas_sys authentication function.
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 confidenceThe GL.iNet AX1800 router firmware versions 4.0.0 through 4.4.x contain insecure permissions in the gl_nas_sys authentication function. This allows a remote unauthenticated attacker to execute arbitrary code by sending a crafted script to the affected authentication function, achieving full compromise of the device.
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>= 4.0.0, < 4.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the router admin panel or check the physical device label to confirm the model is GL.iNet AX1800Affected if Device is not a GL.iNet AX1800 model
-
Check installed firmware versionLog into the router web interface and navigate to System > Firmware or Status page to view the current firmware version numberAffected if Firmware version is 4.0.0 or higher but lower than 4.5.0
-
Verify gl_nas_sys feature statusCheck router settings for gl_nas_sys or NAS-related configuration. This is typically found under Storage, NAS, or USB settings in the web interfaceAffected if gl_nas_sys feature or NAS functionality is enabled on the device
-
Assess network exposure of web interfaceDetermine if the router web administration interface is accessible from WAN/external networks. Check firewall rules or port forwarding settingsAffected if Web interface is exposed to untrusted networks without VPN or access restrictions
The environment is affected if the device is an AX1800 running firmware between 4.0.0 and 4.4.x with gl_nas_sys enabled and the web interface accessible from external networks.
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.
dbcve · scoped4.5.0
Upgrade GL.iNet AX1800 firmware to version 4.5.0 or later to resolve the insecure permissions vulnerability in the gl_nas_sys authentication function. If immediate patching is not possible, restrict external access to the router's web interface and NAS services.
GL.iNet AX1800 firmware >= 4.5.0
- Verify current firmware version on GL.iNet AX1800 device via web interface or CLI
- Download firmware version 4.5.0 or later from the official GL.iNet support website
- Access the device's administrative web interface
- Navigate to the Firmware Upgrade section
- Upload the downloaded firmware file
- Allow the device to complete the upgrade process and reboot
- Verify the new firmware version is installed and the device is operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47463 — 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-2023-47463 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