CVE-2014-0090
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 · uneditedSession fixation vulnerability in Foreman before 1.4.2 allows remote attackers to hijack web sessions via the session id cookie.
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 confidenceSession fixation vulnerability in Foreman allows attackers to predefine a session ID (typically via a cookie) before user authentication. After the user logs in, the attacker can use the same session ID to hijack the authenticated session and gain unauthorized access to the user's account.
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.4.1= 1.0= 1.1= 1.2.0= 1.2.1= 1.2.2= 1.2.3= 1.4.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 Foreman versionCheck the installed Foreman version by navigating to the web UI About page (typically at /about) or by checking the version file in the installation directory (often /usr/share/foreman/.version or via 'foreman-version' command)Affected if The installed version is 1.0, 1.1, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.4.0, or any version <= 1.4.1
-
Verify session ID regeneration behaviorReview the application source code or session management configuration to determine if session IDs are regenerated upon successful authentication. Check session_controller.rb or similar authentication-related code for 'regenerate_session_id' or 'reset_session' calls after loginAffected if No session ID regeneration occurs after successful authentication - the original pre-login session ID remains unchanged
-
Test session cookie persistenceSet a custom session cookie value before authentication, then authenticate as a valid user and examine the session cookie value after login completes. Compare the pre-login and post-login session IDsAffected if The session ID remains identical before and after authentication, indicating vulnerability to session fixation
A user is affected if their Foreman version is 1.4.1 or earlier (specifically 1.0, 1.1, 1.2.0-1.2.3, 1.4.0, or <=1.4.1) and the application does not regenerate session IDs upon 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 dataUpgrade Foreman to version 1.4.2 or later, which should contain proper session ID regeneration upon successful authentication to prevent session fixation attacks.
- 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-2014-0090 — 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-2014-0090 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