CVE-2024-41643
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 · uneditedAn issue in Arris NVG443B 9.3.0h3d36 allows a physically proximate attacker to execute arbitrary code via the cshell login component.
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 Arris NVG443B router firmware 9.3.0h3d36 contains a vulnerability in the cshell login component that allows a physically proximate attacker to execute arbitrary code. This suggests either an authentication bypass or command injection flaw in the cshell service, which is accessible locally on the device.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 the device modelCheck the router label or access the admin interface to confirm the device is an Arris NVG443B modelAffected if The device is not an Arris NVG443B, then this specific CVE does not apply
-
Determine the firmware versionAccess the router admin interface (typically at 192.168.1.1) and navigate to the status or firmware information page to find the installed firmware version, or check the label on the device for version markingsAffected if The firmware version is 9.3.0h3d36 exactly, indicating this specific vulnerable release
-
Check if cshell service is accessibleAttempt to access the cshell service locally on the device through the serial console or by connecting to the device directly via UART/JTAG interfaces if available, or check running processes for cshellAffected if The cshell login component is running and accessible on the device
-
Verify cshell authentication configurationIf cshell is accessible, examine the login configuration files or attempt to log in with default credentials to check for authentication bypass, or inspect cshell logs for failed login attempts that may indicate injection vulnerabilitiesAffected if The cshell service does not properly authenticate users or allows command injection through login fields
A user is affected if they have an Arris NVG443B router running firmware version 9.3.0h3d36 with the cshell service enabled and accessible, allowing a physically proximate attacker to potentially execute arbitrary code through the cshell login component.
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 physical access to the Arris NVG443B device and apply any vendor firmware updates if available. If cshell is not required for operations, disable the service to reduce attack surface.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41643 — 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-41643 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