CVE-2024-5403
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 · uneditedASKEY 5G NR Small Cell fails to properly filter user input for certain functionality, allowing remote attackers with administrator privilege to execute arbitrary system commands on the remote server.
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 confidenceASKEY 5G NR Small Cell contains a command injection vulnerability due to improper input filtering in certain administrative functions. An authenticated attacker with administrator privileges can inject arbitrary system commands through unsanitized user input, achieving remote code execution on the underlying operating system.
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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 the device modelAccess the device management interface or check the device label/hardware for ASKEY 5G NR Small Cell branding. Alternatively, run 'grep -i askey' or check SNMP sysDescr on the device IP.Affected if The device is an ASKEY 5G NR Small Cell product
-
Determine the firmware versionLog into the administrative web interface and navigate to System > Firmware or Status > About. From CLI, run 'show version' or 'cat /proc/version' if accessible.Affected if The firmware version cannot be verified or is earlier than the vendor patched version
-
Verify administrative interface exposureCheck if TCP ports 443, 80, 22, or other management ports are open to untrusted networks. Run 'nmap -p 80,443,22 <device_ip>' from an external location.Affected if Administrative interfaces are reachable from untrusted networks
-
Check authentication configurationReview user accounts in the admin panel under User Management or AAA settings. Verify if default credentials are still active or if weak password policies are in use.Affected if Default administrative credentials are in use or the admin panel allows weak passwords
-
Inspect for indicators of compromiseReview system logs for unusual commands, unexpected shell invocations, or unfamiliar processes. Check /var/log or the device logging interface for 'system(', 'exec(', or similar injection patterns.Affected if Logs show arbitrary command execution or suspicious input patterns in administrative functions
If the device is an ASKEY 5G NR Small Cell with exposed admin interface and the firmware version is unverified or older than the patched release, the environment is likely affected by this command injection vulnerability.
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 dataRestrict administrative access to trusted IPs only, disable unnecessary management interfaces, and apply vendor-provided firmware patches when available. Implement strict input validation on all user-supplied parameters.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5403 — 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-5403 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