medium
4.3
Advisory Published
Updated

CVE-2013-3374

First published: Fri Aug 23 2013(Updated: )

Unspecified vulnerability in Request Tracker (RT) 3.8.x before 3.8.17 and 4.0.x before 4.0.13, when using the Apache::Session::File session store, allows remote attackers to obtain sensitive information (user preferences and caches) via unknown vectors, related to a "limited session re-use."

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Best Practical Solutions Request Tracker=4.0.0
Best Practical Solutions Request Tracker=4.0.0-rc1
Best Practical Solutions Request Tracker=4.0.0-rc2
Best Practical Solutions Request Tracker=4.0.0-rc3
Best Practical Solutions Request Tracker=4.0.0-rc4
Best Practical Solutions Request Tracker=4.0.0-rc5
Best Practical Solutions Request Tracker=4.0.0-rc6
Best Practical Solutions Request Tracker=4.0.0-rc7
Best Practical Solutions Request Tracker=4.0.0-rc8
Best Practical Solutions Request Tracker=4.0.1
Best Practical Solutions Request Tracker=4.0.1-rc1
Best Practical Solutions Request Tracker=4.0.1-rc2
Best Practical Solutions Request Tracker=4.0.2
Best Practical Solutions Request Tracker=4.0.2-rc1
Best Practical Solutions Request Tracker=4.0.2-rc2
Best Practical Solutions Request Tracker=4.0.3
Best Practical Solutions Request Tracker=4.0.3-rc1
Best Practical Solutions Request Tracker=4.0.3-rc2
Best Practical Solutions Request Tracker=4.0.4
Best Practical Solutions Request Tracker=4.0.5
Best Practical Solutions Request Tracker=4.0.5-rc1
Best Practical Solutions Request Tracker=4.0.6
Best Practical Solutions Request Tracker=4.0.7
Best Practical Solutions Request Tracker=4.0.7-rc1
Best Practical Solutions Request Tracker=4.0.8
Best Practical Solutions Request Tracker=4.0.8-rc1
Best Practical Solutions Request Tracker=4.0.8-rc2
Best Practical Solutions Request Tracker=4.0.9
Best Practical Solutions Request Tracker=4.0.10
Best Practical Solutions Request Tracker=4.0.11
Best Practical Solutions Request Tracker=4.0.12
Best Practical Solutions Request Tracker=3.8.0
Best Practical Solutions Request Tracker=3.8.0-preflight1
Best Practical Solutions Request Tracker=3.8.0-rc1
Best Practical Solutions Request Tracker=3.8.0-rc2
Best Practical Solutions Request Tracker=3.8.0-rc3
Best Practical Solutions Request Tracker=3.8.1
Best Practical Solutions Request Tracker=3.8.1-preflight0
Best Practical Solutions Request Tracker=3.8.1-rc1
Best Practical Solutions Request Tracker=3.8.1-rc2
Best Practical Solutions Request Tracker=3.8.1-rc3
Best Practical Solutions Request Tracker=3.8.1-rc4
Best Practical Solutions Request Tracker=3.8.1-rc5
Best Practical Solutions Request Tracker=3.8.2
Best Practical Solutions Request Tracker=3.8.2-rc1
Best Practical Solutions Request Tracker=3.8.2-rc2
Best Practical Solutions Request Tracker=3.8.3
Best Practical Solutions Request Tracker=3.8.3-rc1
Best Practical Solutions Request Tracker=3.8.3-rc2
Best Practical Solutions Request Tracker=3.8.4
Best Practical Solutions Request Tracker=3.8.4-rc1
Best Practical Solutions Request Tracker=3.8.5
Best Practical Solutions Request Tracker=3.8.6
Best Practical Solutions Request Tracker=3.8.6-rc1
Best Practical Solutions Request Tracker=3.8.7
Best Practical Solutions Request Tracker=3.8.7-rc1
Best Practical Solutions Request Tracker=3.8.8
Best Practical Solutions Request Tracker=3.8.8-rc2
Best Practical Solutions Request Tracker=3.8.8-rc3
Best Practical Solutions Request Tracker=3.8.8-rc4
Best Practical Solutions Request Tracker=3.8.9
Best Practical Solutions Request Tracker=3.8.9-rc1
Best Practical Solutions Request Tracker=3.8.9-rc2
Best Practical Solutions Request Tracker=3.8.9-rc3
Best Practical Solutions Request Tracker=3.8.10
Best Practical Solutions Request Tracker=3.8.10-rc1
Best Practical Solutions Request Tracker=3.8.11
Best Practical Solutions Request Tracker=3.8.11-rc1
Best Practical Solutions Request Tracker=3.8.11-rc2
Best Practical Solutions Request Tracker=3.8.12
Best Practical Solutions Request Tracker=3.8.13
Best Practical Solutions Request Tracker=3.8.13-rc1
Best Practical Solutions Request Tracker=3.8.13-rc2
Best Practical Solutions Request Tracker=3.8.14
Best Practical Solutions Request Tracker=3.8.14-rc1
Best Practical Solutions Request Tracker=3.8.15
Best Practical Solutions Request Tracker=3.8.16

Remedy

http://lists.bestpractical.com/pipermail/rt-announce/2013-May/000226.html

Remedy

http://lists.bestpractical.com/pipermail/rt-announce/2013-May/000227.html

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2013-3374?

    CVE-2013-3374 has a moderate severity level due to its impact on user privacy and data security.

  • How do I fix CVE-2013-3374?

    To fix CVE-2013-3374, upgrade to Request Tracker version 3.8.17 or 4.0.13 or later.

  • What types of information can be exposed in CVE-2013-3374?

    CVE-2013-3374 allows remote attackers to potentially access sensitive user information, such as preferences and caches.

  • Which versions of Request Tracker are affected by CVE-2013-3374?

    CVE-2013-3374 affects Request Tracker versions 3.8.x before 3.8.17 and 4.0.x before 4.0.13.

  • Can CVE-2013-3374 be exploited remotely?

    Yes, CVE-2013-3374 can be exploited by remote attackers, making it a significant risk.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203