dbcve.org
MantisApplication

CVE-2005-3339

HIGH · 7.2 CVSS v2.0 Published 2005-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Mantis before 0.19.3 caches the User ID longer than necessary, which has unknown impact and attack vectors.

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 confidence

Mantis before 0.19.3 retains user ID information in cache beyond the intended duration. This session management flaw could allow an attacker to potentially hijack or reuse stale user identifiers, though the specific attack vector remains undefined in available documentation.

MitigationUpgrade Mantis to version 0.19.3 or later. Review and invalidate all active sessions after upgrading.

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
MantisApplication
Affected:= 0.19.0= 0.19.0_rc1= 0.19.0a1= 0.19.0a2= 0.19.1= 0.19.2= 0.19.3

CVSS 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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Mantis installation directory
    Identify the web root directory where Mantis is installed. Check for the presence of files like 'config.php' or a directory named 'mantis' that contains Mantis core files.
    Affected if Cannot locate Mantis installation to verify version
  2. Identify installed Mantis version
    Open the Mantis 'config.php' file or look for a version file in the Mantis directory. The version is often displayed on the login page footer or can be found in a 'version.php' or similar file within the installation.
    Affected if Version cannot be determined from installation files
  3. Compare version against affected range
    Check if the installed version is 0.19.0, 0.19.0_rc1, 0.19.0a1, 0.19.0a2, 0.19.1, or 0.19.2. These versions are affected by the session caching flaw.
    Affected if Installed version matches any of: 0.19.0, 0.19.0_rc1, 0.19.0a1, 0.19.0a2, 0.19.1, or 0.19.2
  4. Verify session management is active
    Confirm that user authentication and session management are enabled in the Mantis configuration. This vulnerability only affects environments where users can log in and maintain sessions.
    Affected if Mantis is configured with user authentication and sessions are in use

A user is affected if their Mantis installation version is 0.19.0 through 0.19.2 and user login sessions are active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Mantis to version 0.19.3 or later. Review and invalidate all active sessions after upgrading.

Fix this in Mantis Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-3339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-3339 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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