Sensitive Information Exposure in OTRS2: CVE-2010-4760

otrs2 Updated 02 Oct 2025

Summary

18/03/2011
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2010-4760: Open Ticket Request System (OTRS) before 3.0.0-beta6 adds email-notification-ext articles to tickets during processing of event-based notifications, which allows remote authenticated users to obtain potentially sensitive... Affects otrs2 versions < 3.0.8+dfsg1-1. Fixed in 3.0.8+dfsg1-1. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Open Ticket Request System (OTRS) is a widely used open-source ticketing system that helps organizations manage customer support and service requests. OTRS2, a version of this system, provides functionalities such as ticket management, email notifications, and reporting. However, prior to version 3.0.0-beta6, OTRS2 had a vulnerability that allowed remote authenticated users to access potentially sensitive information through event-based notifications.

Vulnerability Detail

The vulnerability identified as CVE-2010-4760 in OTRS2 arises from the improper handling of email-notification-ext articles during the processing of event-based notifications. This flaw allows authenticated users to read tickets that they should not have access to, potentially exposing sensitive information. The issue is rooted in the way OTRS2 manages notifications, leading to unauthorized information disclosure.

How To Fix

Minimum fixed version

3.0.8+dfsg1-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade otrs2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, administrators can restrict access to the ticketing system or disable email notifications until the system is updated to a secure version.

Conclusion

CVE-2010-4760 is a significant vulnerability in OTRS2 that can lead to unauthorized access to sensitive information. It is crucial for users to update to the patched version to mitigate this risk. Additionally, utilizing tools like Vulert can enhance your security posture by providing real-time vulnerability monitoring.

See every vulnerability recorded for otrs2 →

Share this vulnerability

FAQ

CVE-2010-4760 is a vulnerability in OTRS2 that allows remote authenticated users to access sensitive information by reading tickets through event-based notifications.

If you are using a version of OTRS2 prior to 3.0.0-beta6, your installation is vulnerable. You can check your version by running the command 'otrs.Console.pl Admin::SystemInfo'.

The primary risk is unauthorized access to sensitive ticket information, which could lead to data breaches and compromise user privacy.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring access to the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability by simply uploading your manifest file, such as package-lock.json.

Related vulnerabilities

Recent vulnerabilities recorded for otrs2.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

3.0.8+dfsg1-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade otrs2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback