medium
4
CWE
264
Advisory Published
Updated

CVE-2010-4761

First published: Fri Mar 18 2011(Updated: )

The customer-interface ticket-print dialog in Open Ticket Request System (OTRS) before 3.0.0-beta3 does not properly restrict customer-visible data, which allows remote authenticated users to obtain potentially sensitive information from the (1) responsible, (2) owner, (3) accounted time, (4) pending until, and (5) lock fields by reading this dialog.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
OTRS<=3.0.0
OTRS=0.5-beta1
OTRS=0.5-beta2
OTRS=0.5-beta3
OTRS=0.5-beta4
OTRS=0.5-beta5
OTRS=0.5-beta6
OTRS=0.5-beta7
OTRS=0.5-beta8
OTRS=1.0-rc1
OTRS=1.0-rc2
OTRS=1.0-rc3
OTRS=1.0.0
OTRS=1.0.1
OTRS=1.0.2
OTRS=1.1-rc1
OTRS=1.1.0-rc1
OTRS=1.1.0-rc2
OTRS=1.1.1
OTRS=1.1.2
OTRS=1.1.3
OTRS=1.1.4
OTRS=1.2.0-beta1
OTRS=1.2.0-beta2
OTRS=1.2.0-beta3
OTRS=1.2.1
OTRS=1.2.2
OTRS=1.2.3
OTRS=1.2.4
OTRS=1.3.0-beta1
OTRS=1.3.0-beta2
OTRS=1.3.0-beta3
OTRS=1.3.0-beta4
OTRS=1.3.1
OTRS=1.3.2
OTRS=1.3.3
OTRS=2.0.0
OTRS=2.0.0-beta1
OTRS=2.0.0-beta2
OTRS=2.0.0-beta4
OTRS=2.0.0-beta5
OTRS=2.0.0-beta6
OTRS=2.0.1
OTRS=2.0.2
OTRS=2.0.3
OTRS=2.0.4
OTRS=2.0.5
OTRS=2.1.0-beta1
OTRS=2.1.0-beta2
OTRS=2.1.1
OTRS=2.1.2
OTRS=2.1.3
OTRS=2.1.4
OTRS=2.1.5
OTRS=2.1.6
OTRS=2.1.7
OTRS=2.1.8
OTRS=2.1.9
OTRS=2.2.0-beta1
OTRS=2.2.0-beta2
OTRS=2.2.0-beta3
OTRS=2.2.0-beta4
OTRS=2.2.0-rc1
OTRS=2.2.1
OTRS=2.2.2
OTRS=2.2.3
OTRS=2.2.4
OTRS=2.2.5
OTRS=2.2.6
OTRS=2.2.7
OTRS=2.2.8
OTRS=2.2.9
OTRS=2.3.0-beta1
OTRS=2.3.0-beta2
OTRS=2.3.0-beta3
OTRS=2.3.0-beta4
OTRS=2.3.0-rc1
OTRS=2.3.1
OTRS=2.3.2
OTRS=2.3.3
OTRS=2.3.4
OTRS=2.3.5
OTRS=2.3.6
OTRS=2.4.0-beta1
OTRS=2.4.0-beta2
OTRS=2.4.0-beta3
OTRS=2.4.0-beta4
OTRS=2.4.0-beta5
OTRS=2.4.0-beta6
OTRS=2.4.1
OTRS=2.4.2
OTRS=2.4.3
OTRS=2.4.4
OTRS=2.4.5
OTRS=2.4.6
OTRS=2.4.7
OTRS=2.4.8
OTRS=2.4.9
OTRS=2.4.10
OTRS=3.0.0-beta1

Remedy

http://bugs.otrs.org/show_bug.cgi?id=5875

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-2010-4761?

    The severity of CVE-2010-4761 is classified as moderate, as it could allow authenticated users to access sensitive information.

  • How do I fix CVE-2010-4761?

    To fix CVE-2010-4761, upgrade to OTRS version 3.0.0-beta3 or later.

  • What versions of OTRS are affected by CVE-2010-4761?

    CVE-2010-4761 affects OTRS versions prior to 3.0.0-beta3, including several beta and release candidate versions.

  • Is CVE-2010-4761 remotely exploitable?

    Yes, CVE-2010-4761 can be exploited by remote authenticated users to view sensitive data.

  • What types of information might be exposed due to CVE-2010-4761?

    CVE-2010-4761 may expose potentially sensitive information such as ticket ownership, accounting time, and responsible parties.

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