CVE-2024-36783
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 · uneditedTOTOLINK LR350 V9.3.5u.6369_B20220309 was discovered to contain a command injection via the host_time parameter in the NTPSyncWithHost 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 TOTOLINK LR350 router firmware V9.3.5u.6369_B20220309 contains a command injection vulnerability in the NTPSyncWithHost function. The host_time parameter is not properly sanitized before being passed to system calls, allowing an unauthenticated attacker to execute arbitrary operating system commands.
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= 9.3.5u.6369_b20220309CVSS 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 the firmware version running on the TOTOLINK LR350Access the router's web management interface and navigate to the System or Status page to view the firmware version. Alternatively, check the /etc/version file or the uboot environment via telnet or SSH if those services are enabled.Affected if The displayed firmware version matches 9.3.5u.6369_b20220309 exactly.
-
Locate the NTP sync configuration in the web interfaceLog into the router's web interface and find the NTP or Time Settings section under the Advanced or System settings menu.Affected if The NTP Sync With Host or similar feature is present and configurable.
-
Verify the NTPSyncWithHost function is accessibleAttempt to access the NTPSyncWithHost functionality via the router's web interface or by inspecting the CGI binary (typically /bin/gi or similar) for the host_time parameter handling.Affected if The host_time parameter can be submitted without proper input validation or the function accepts arbitrary string input.
-
Determine if the router web interface is exposed to untrusted networksCheck the router's WAN-facing firewall settings or port forwarding rules to see if HTTP/HTTPS ports (80/443) are accessible from the WAN interface.Affected if The router's management interface is reachable from external IP addresses or untrusted networks.
A user is affected if their TOTOLINK LR350 runs firmware version 9.3.5u.6369_b20220309 and the NTP sync feature is accessible, allowing command injection via the host_time parameter.
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 dataApply any available firmware update from TOTOLINK. If no patch is available, restrict access to the router's web management interface to trusted networks only, or disable the NTP sync functionality if not required.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36783 — 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-36783 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