CVE-2020-26732
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 · uneditedSKYWORTH GN542VF Hardware Version 2.0 and Software Version 2.0.0.16 does not set the Secure flag for the session cookie in an HTTPS session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an HTTP session.
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 confidenceThe SKYWORTH GN542VF router (Hardware v2.0, Software v2.0.0.16) fails to set the Secure flag on session cookies during HTTPS sessions. This allows cookies to be transmitted over insecure HTTP connections where they can be intercepted by man-in-the-middle attackers, potentially enabling session hijacking.
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= 0.94.13CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm router model and firmware versionAccess the router admin interface and check the device information page. Look for model number 'GN542vf' and firmware version. The affected version is Boa Firmware 0.94.13.Affected if The router is a Skyworth GN542vf with Boa Firmware version 0.94.13
-
Verify HTTPS is enabled on the routerLog into the router admin panel and navigate to the security or network settings. Check if HTTPS access is enabled for the web interface.Affected if HTTPS is enabled and used for admin sessions
-
Inspect Set-Cookie headers for the Secure flagUse a web browser developer tools or a packet capture tool (like Wireshark) to capture HTTP traffic when logging into the router over HTTPS. Examine the HTTP response headers for 'Set-Cookie' directives and check if the 'Secure' attribute is present in the cookie string.Affected if Session cookies are set without the Secure attribute even when the connection is HTTPS
-
Test cookie transmission over HTTPAttempt to access the router login page over HTTP (non-encrypted). If session cookies are transmitted or can be received over the insecure HTTP connection, the Secure flag is missing.Affected if Session cookies can be observed or transmitted over an unencrypted HTTP connection
You are affected if you are using a Skyworth GN542VF router with Boa Firmware 0.94.13 and session cookies do not contain the Secure attribute during HTTPS sessions.
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 dataConfigure the session cookie to include the Secure attribute, ensuring it is only transmitted over encrypted HTTPS connections.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26732 — 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-2020-26732 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