CVE-2015-5384
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 · uneditedAxiomSL's Axiom Google Web Toolkit module 9.5.3 and earlier is vulnerable to a Session Fixation attack.
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 confidenceAxiomSL's Axiom Google Web Toolkit module versions 9.5.3 and earlier is vulnerable to Session Fixation, where an attacker can set or pre-determine a user's session identifier before authentication, allowing the attacker to hijack the user's session after successful login.
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.5.3CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 installed AxiomSL Axiom versionLocate the Axiom application version information through the application itself, version file, or system inventory. Common locations include the application's about/help section, a version.txt file in the installation directory, or the software asset management system.Affected if The installed version is 9.5.3 or any earlier version (9.5.3, 9.5.2, 9.5.1, etc.)
-
Confirm Google Web Toolkit module is enabledCheck the AxiomSL Axiom configuration to determine if the Google Web Toolkit (GWT) module is actively loaded and used. This is typically found in the module configuration files or the application's feature list.Affected if The GWT module is enabled and the application version is 9.5.3 or earlier
-
Verify session ID regeneration after authenticationInspect the application's session management configuration or perform a test login to observe whether a new session identifier is generated upon successful authentication. Compare the session ID before and after login.Affected if The session ID remains the same before and after authentication, indicating session fixation is possible
-
Check session cookie configurationExamine the session cookie settings (such as JSESSIONID or similar) to determine if the secure and httpOnly flags are properly configured.Affected if Session cookies lack the secure flag, httpOnly flag, or both, making them vulnerable to theft via JavaScript or network interception
The environment is affected if AxiomSL Axiom version 9.5.3 or earlier is installed with the GWT module enabled, and session IDs are not regenerated after successful authentication.
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 dataRegenerate session IDs upon successful authentication and invalidate the previous session. Additionally, ensure session cookies are configured with secure and httpOnly flags and consider implementing session timeout policies.
- 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-2015-5384 — 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-5384 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