CVE-2022-38555
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 · uneditedLinksys E1200 v1.0.04 is vulnerable to Buffer Overflow via ej_get_web_page_name.
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 confidenceA buffer overflow vulnerability exists in the Linksys E1200 v1.0.04 router firmware's web interface function ej_get_web_page_name. The function fails to properly validate input bounds when processing web page name requests, allowing an attacker to overflow a fixed-size buffer via specially crafted HTTP requests. This could allow remote code execution with elevated privileges on 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= 1.0.04CVSS 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 device modelCheck the router label or web interface for the model number to confirm it is a Linksys E1200Affected if The device is a Linksys E1200 router
-
Check the firmware versionAccess the router web interface (typically at 192.168.1.1) and look for the firmware version in the status or administration section, or use the command 'nvram get firmware_version' via telnet/ssh if availableAffected if The firmware version is 1.0.04
-
Verify the web interface is accessibleAttempt to access the router web interface via HTTP on the local network (default port 80)Affected if The web interface responds to HTTP requests, indicating the vulnerable function ej_get_web_page_name is exposed
-
Confirm remote web management statusCheck the router administration settings for 'Remote Management' or 'Web Access' settings that allow access from outside the local networkAffected if Remote web management is enabled, making the vulnerable web interface accessible from external networks
A user is affected if they have a Linksys E1200 router running firmware version 1.0.04 with an accessible web interface, particularly if remote management is enabled.
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 · scopedApply available firmware updates from Linksys for the E1200; if no patch is available, consider replacing the device or implementing network segmentation to limit exposure to untrusted networks. Disable remote web management or limit access to trusted IP addresses.
- This vulnerability in Linksys E1200 v1.0.04 has no documented vendor-provided patch or firmware update.
- Consider replacing the affected device with a currently supported router model that receives security updates.
- If replacement is not immediately possible, place the device on an isolated network segment to limit potential impact from exploitation.
- Monitor the device manufacturer and security communities for any future firmware releases addressing CVE-2022-38555.
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2022-38555 — 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-38555 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