Vulnerability in otrs2 Package - Missing Challenge Token Checks and SQL Injection
Summary
DSA-2867-1: otrs2 - several. Affects otrs2 versions < 2.4.9+dfsg1-3+squeeze5. Fixed in 2.4.9+dfsg1-3+squeeze5. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
otrs2 is an Open Ticket Request System used for managing customer support tickets. It provides a web-based interface for customers and agents to create, view, and respond to tickets. The package is widely used in various organizations to streamline their support processes. However, a vulnerability has been discovered in otrs2 that allows attackers to bypass challenge token checks and inject SQL code through the ticket search URL.
Vulnerability Detail
The first vulnerability, identified as CVE-2014-1694, allows an attacker who has taken over the session of a logged-in customer to create tickets and send follow-ups to existing tickets due to missing challenge token checks. This can lead to unauthorized actions being performed by the attacker.
The second vulnerability, identified as CVE-2014-1471, enables an attacker with a valid customer or agent login to inject SQL code through the ticket search URL. By exploiting this vulnerability, an attacker can execute arbitrary SQL queries, potentially leading to unauthorized access or data manipulation.
How To Fix
Minimum fixed version
2.4.9+dfsg1-3+squeeze5
This is the first release that contains the fix.
sudo apt-get install --only-upgrade otrs2Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
The otrs2 package is vulnerable to missing challenge token checks and SQL injection vulnerabilities. To mitigate these risks, it is crucial to update the package to the fixed versions mentioned above. Regularly monitoring and applying security updates is essential to ensure the ongoing security of the otrs2 installation. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for otrs2 →
FAQ
The missing challenge token checks vulnerability allows an attacker to perform actions on behalf of a logged-in customer, such as creating tickets or sending follow-ups. This can lead to unauthorized actions being performed and potential data manipulation.
An attacker with a valid customer or agent login can inject SQL code through the ticket search URL. By crafting malicious input, the attacker can execute arbitrary SQL queries, potentially gaining unauthorized access or manipulating the database.
No specific workarounds have been mentioned for these vulnerabilities. It is recommended to update the otrs2 package to the fixed versions provided.
The oldstable distribution (squeeze), stable distribution (wheezy), testing distribution (jessie), and unstable distribution (sid) are affected by these vulnerabilities. The fixed versions mentioned earlier should be applied to the respective distributions.
More information about these vulnerabilities can be found in the Common Vulnerabilities and Exposures (CVE) database. The CVE identifiers for these vulnerabilities are CVE-2014-1694 and CVE-2014-1471.
Related vulnerabilities
Recent vulnerabilities recorded for otrs2.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
