CVE-2008-3102
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 · uneditedMantis 1.1.x through 1.1.2 and 1.2.x through 1.2.0a2 does not set the secure flag for the session cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this 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 confidenceMantisBT versions 1.1.x through 1.1.2 and 1.2.x through 1.2.0a2 fail to set the 'secure' flag on the session cookie. This allows the session identifier to be transmitted over insecure HTTP connections even when the user authenticates over HTTPS, enabling potential session hijacking through network interception.
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.1.0= 1.1.1= 1.1.2= 1.2.0a1= 1.2.0a2CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Determine installed MantisBT versionLocate the MantisBT installation directory and check the version file, typically named 'version.php' or check the admin page that displays system information. Common paths include /var/www/html/mantis or similar web root directories.Affected if The installed version is 1.1.0, 1.1.1, 1.1.2, 1.2.0a1, or 1.2.0a2.
-
Check PHP session.cookie_secure settingCreate a PHP script with 'phpinfo();' or check php.ini directly for the directive 'session.cookie_secure'. Run 'php -i' from command line or view phpinfo() output via web browser.Affected if session.cookie_secure is set to 0 or not set at all (defaults to 0).
-
Verify actual session cookie secure flag in browserLog into MantisBT over HTTPS using a browser. Use browser developer tools (F12), go to Application or Storage tab, find the session cookie (typically named 'MANTIS_secure_session' or similar), and inspect the 'Secure' attribute.Affected if The session cookie does not have the 'Secure' attribute checked or present.
-
Inspect MantisBT session initialization codeExamine the MantisBT source file that initializes sessions, commonly 'core/session_api.php' or similar session-related files in the installation directory. Look for calls to session_set_cookie_params() or session.cookie_secure configuration.Affected if The code does not set the 'secure' flag via session_set_cookie_params() before session_start() is called.
If running an affected MantisBT version (1.1.0-1.1.2 or 1.2.0a1-1.2.0a2) and the session cookie lacks the Secure flag, the environment is vulnerable to session hijacking over HTTP.
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 dataEnable the 'secure' flag for session cookies by setting session.cookie_secure = 1 in php.ini, or by calling session_set_cookie_params() with the secure flag before session_start() in the MantisBT code.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3102 — 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-2008-3102 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