bestpractical request tracker 3.8.10

CPE Details

bestpractical request tracker 3.8.10
bestpractical
request_tracker
3.8.10
2012-11-12
21h34 +00:00
2013-05-14
21h26 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:bestpractical:request_tracker:3.8.10:*:*:*:*:*:*:*

Informations

Vendor

bestpractical

Product

request_tracker

Version

3.8.10

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-41259 2023-11-02 23h00 +00:00 Best Practical Request Tracker (RT) before 4.4.7 and 5.x before 5.0.5 allows Information Disclosure via fake or spoofed RT email headers in an email message or a mail-gateway REST API call.
7.5
High
CVE-2023-41260 2023-11-02 23h00 +00:00 Best Practical Request Tracker (RT) before 4.4.7 and 5.x before 5.0.5 allows Information Exposure in responses to mail-gateway REST API calls.
7.5
High
CVE-2022-25803 2022-07-14 09h51 +00:00 Best Practical Request Tracker (RT) before 5.0.3 has an Open Redirect via a ticket search.
6.1
Medium
CVE-2022-25802 2022-07-14 09h49 +00:00 Best Practical Request Tracker (RT) before 4.4.6 and 5.x before 5.0.3 allows XSS via a crafted content type for an attachment.
6.1
Medium
CVE-2015-6506 2015-09-03 12h00 +00:00 Cross-site scripting (XSS) vulnerability in the cryptography interface in Request Tracker (RT) before 4.2.12 allows remote attackers to inject arbitrary web script or HTML via a crafted public key.
4.3
CVE-2015-5475 2015-08-14 16h00 +00:00 Multiple cross-site scripting (XSS) vulnerabilities in Request Tracker (RT) 4.x before 4.2.12 allow remote attackers to inject arbitrary web script or HTML via vectors related to the (1) user and (2) group rights management pages.
4.3
CVE-2014-9472 2015-03-09 13h00 +00:00 The email gateway in RT (aka Request Tracker) 3.0.0 through 4.x before 4.0.23 and 4.2.x before 4.2.10 allows remote attackers to cause a denial of service (CPU and disk consumption) via a crafted email.
7.1
CVE-2015-1165 2015-03-09 13h00 +00:00 RT (aka Request Tracker) 3.8.8 through 4.x before 4.0.23 and 4.2.x before 4.2.10 allows remote attackers to obtain sensitive RSS feed URLs and ticket data via unspecified vectors.
5
CVE-2015-1464 2015-03-09 13h00 +00:00 RT (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.
6.4
CVE-2012-6578 2013-07-24 10h00 +00:00 Best Practical Solutions RT 3.8.x before 3.8.15 and 4.0.x before 4.0.8, when GnuPG is enabled with a "Sign by default" queue configuration, uses a queue's key for signing, which might allow remote attackers to spoof messages by leveraging the lack of authentication semantics.
4.3
CVE-2012-6579 2013-07-24 10h00 +00:00 Best Practical Solutions RT 3.8.x before 3.8.15 and 4.0.x before 4.0.8, when GnuPG is enabled, allows remote attackers to configure encryption or signing for certain outbound e-mail, and possibly cause a denial of service (loss of e-mail readability), via an e-mail message to a queue's address.
6.4
CVE-2012-6580 2013-07-24 10h00 +00:00 Best Practical Solutions RT 3.8.x before 3.8.15 and 4.0.x before 4.0.8, when GnuPG is enabled, does not ensure that the UI labels unencrypted messages as unencrypted, which might make it easier for remote attackers to spoof details of a message's origin or interfere with encryption-policy auditing via an e-mail message to a queue's address.
4.3
CVE-2012-6581 2013-07-24 10h00 +00:00 Best Practical Solutions RT 3.8.x before 3.8.15 and 4.0.x before 4.0.8, when GnuPG is enabled, allows remote attackers to bypass intended restrictions on reading keys in the product's keyring, and trigger outbound e-mail messages signed by an arbitrary stored secret key, by leveraging a UI e-mail signing privilege.
4.3
CVE-2013-3525 2013-05-10 19h00 +00:00 SQL injection vulnerability in Approvals/ in Request Tracker (RT) 4.0.10 and earlier allows remote attackers to execute arbitrary SQL commands via the ShowPending parameter. NOTE: the vendor disputes this issue, stating "We were unable to replicate it, and the individual that reported it retracted their report," and "we had verified that the claimed exploit did not function according to the author's claims.
7.5