A vulnerability was found in Best Practical Request Tracker up to 4.0.5 (Ticket Tracking Software) and classified as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a access control vulnerability (Stored). Using CWE to declare the problem leads to CWE-264. Impacted is integrity. The summary by CVE is:

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.

The weakness was published 07/24/2013 (Website). It is possible to read the advisory at lists.bestpractical.com. The identification of this vulnerability is CVE-2012-6581 since 07/23/2013. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 62722 (Debian DSA-2567-1 : request-tracker3.8 - several vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks.

Upgrading to version 4.0.6 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (62722). Similar entries are available at 62906, 62905, 62904 and 62902.

Productinfo

Type

• Ticket Tracking Software

Vendor

• Best Practical

Name

• Request Tracker

Version

• 4.0.0
• 4.0.1
• 4.0.2
• 4.0.3
• 4.0.4
• 4.0.5

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion