CVE-2015-7924
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 · uneditedeWON devices with firmware before 10.1s0 do not trigger the discarding of browser session data in response to a log-off action, which makes it easier for remote attackers to obtain access by leveraging an unattended workstation.
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 confidenceeWON industrial networking devices with firmware versions prior to 10.1s0 fail to invalidate browser session data (cookies, tokens, cached credentials) when a user logs out. This session management flaw allows an attacker with physical access to an unattended workstation to reuse the stale session data and authenticate as the original user without credentials.
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<= 10.0s0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 eWON device firmware versionAccess the eWON web interface or use the eWON configuration tool to view the firmware version information. Typically found in the device status or system information page.Affected if Firmware version is 10.0s0 or earlier (any version listed as 10.0s0, 9.x, or lower)
-
Verify web-based remote access is enabledCheck the eWON configuration for 'Remote Access' or 'VPN' settings. Look for features like 'Web API', 'Flexy IO', or 'BASIC' web server settings in the device configuration.Affected if Remote web access features are enabled on the device
-
Check for active user accounts with web login capabilityReview user account configuration in the eWON device settings. Look for accounts with web interface access or remote access permissions.Affected if User accounts exist with web or remote login permissions
-
Confirm session persistence after logoutLog in to the eWON web interface, then log out. Attempt to access protected resources using the previous session cookies or URL tokens without re-authenticating.Affected if Stale session remains valid after logout (can access without credentials)
The environment is affected if the eWON device runs firmware version 10.0s0 or earlier AND has web-based remote access or user accounts configured, since the session invalidation flaw exists in those versions.
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 dataUpgrade eWON firmware to version 10.1s0 or later to ensure proper session invalidation on logout. If upgrading is not immediately feasible, enforce strict workstation session timeout policies and physically secure console access.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7924 — 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-2015-7924 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