FedoraOperating system · Fedoraproject
CVE-2015-1464
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 · uneditedRT (aka Request Tracker) before 4.0.23 and 4.2.x before 4.2.10 allows remote attackers to hijack sessions via an RSS feed URL.
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 confidenceRT (Request Tracker) before 4.0.23 and 4.2.x before 4.2.10 contains a session hijacking vulnerability in its RSS feed functionality. Attackers can craft malicious RSS feed URLs to capture or predict session identifiers, allowing unauthorized access to user sessions.
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
FedoraOperating system
= 21= 22<= 4.0.22= 4.2.0= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 4.2.5= 4.2.6= 4.2.7= 4.2.8= 4.2.9CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Locate the Request Tracker installationCheck for RT installation directories such as /opt/rt4, /usr/local/rt, or consult your system package manager for installed RT packages using 'rpm -qa | grep -i request-tracker' or 'dpkg -l | grep -i rt'Affected if RT is not installed on the system
-
Identify the installed RT versionExamine the RT.pm file in the lib directory, for example 'cat /opt/rt4/lib/RT.pm | grep '^our \$VERSION' or check the version file in the distribution. If installed via package manager, use 'rpm -q request-tracker' or 'dpkg -s request-tracker4'Affected if The version number returned is 4.0.22 or lower, or falls within 4.2.0 through 4.2.9
-
Confirm RSS feed functionality is accessibleCheck if the RSS feed endpoint is available by accessing a URL path such as /NoAuth/rss/ or /RSS/index.html on your RT server, or verify that the 'Web' interface includes RSS feed links in the navigationAffected if RSS feeds are accessible without authentication or the RSS feed module is loaded in the RT web interface
-
Check session configuration for RSS feedsInspect the RT_SiteConfig.pm or RT_Config.pm file for any session-related settings, particularly looking for 'WebRemoteUserAuth' or session cookie configuration that may affect RSS feed securityAffected if Session identifiers are passed via URL parameters in RSS feeds or session handling is not configured to use secure cookies only
You are affected if your installed RT version is 4.0.22 or lower, or between 4.2.0 and 4.2.9, and the RSS feed functionality is enabled and accessible on your server.
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 RT to version 4.0.23, 4.2.10, or later. Verify that RSS feed functionality uses secure session handling after the upgrade.
Fix this in Fedora
Scoped from the published advisory
- 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-1464 — 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-1464 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