CVE-2022-36786
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 · uneditedDLINK - DSL-224 Post-auth RCE. DLINK router version 3.0.8 has an interface where you can configure NTP servers (Network Time Protocol) via jsonrpc API. It is possible to inject a command through this interface that will run with ROOT permissions on the router.
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 · high confidenceCommand injection vulnerability in the NTP server configuration feature of D-Link DSL-224 router firmware version 3.0.8 allows authenticated attackers to execute arbitrary operating system commands with root privileges through the jsonrpc API by injecting shell metacharacters into NTP server parameters.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 web interface and look for the model number in the status or device info pageAffected if The device is a D-Link DSL-224 router
-
Determine the firmware versionIn the router web interface, navigate to Status or System Info page and note the firmware version number displayedAffected if Firmware version is 3.0.8 or any version of the 3.0.x branch
-
Verify jsonrpc API accessibilityAttempt to access the router's web interface or check if port 80/443 is listening on the WAN interface. Try sending a POST request to the jsonrpc endpoint (typically /jsonrpc) with a test payload to see if it respondsAffected if The jsonrpc API is reachable from an untrusted network (WAN) or from an compromised internal host
-
Confirm NTP server configuration is exposedIn the router web interface, locate the NTP settings under Time or NTP configuration section. Note if these settings can be modified and if they accept custom server addressesAffected if NTP server configuration parameters are accessible and accept user-supplied input
-
Check for existing unauthorized accessReview router logs for any suspicious commands or unexpected entries in the system log. Look for shell metacharacters (such as ; | ` $ ( ) ) in NTP server fields or command historyAffected if Logs show commands containing shell metacharacters or unexpected NTP server configurations
The environment is affected if the device is a D-Link DSL-224 running firmware 3.0.8 with the jsonrpc API accessible to untrusted users and NTP server configuration is available for modification.
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 vendor firmware update when available; until then, restrict administrative access to the router's web interface to trusted IPs only via firewall rules or disable remote management.
- 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-2022-36786 — 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-2022-36786 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