What is the severity of CVE-2013-6241?

CVE-2013-6241 has a high severity rating as it allows unauthorized access to sensitive birthday information.

How do I fix CVE-2013-6241?

To fix CVE-2013-6241, upgrade Open-Xchange App Suite to version 7.2.2-rev25 or later, or 7.4.0-rev14 or later.

Who is affected by CVE-2013-6241?

Users of Open-Xchange App Suite versions 7.2.0, 7.2.1, 7.2.2, and 7.4.0 are affected by CVE-2013-6241.

What kind of exploitation is possible with CVE-2013-6241?

CVE-2013-6241 can be exploited by remote authenticated users to access sensitive birthday data through improper SQL query construction.

Is there a workaround for CVE-2013-6241?

There is no official workaround for CVE-2013-6241; applying the latest patch is the recommended solution.

Vulnerability/
CVE-2013-6241

medium

CWE

200

27/12/2014

6/8/2024

CVE-2013-6241: Infoleak

First published: Sat Dec 27 2014(Updated: )

The Birthday widget in the backend in Open-Xchange (OX) AppSuite 7.2.x before 7.2.2-rev25 and 7.4.x before 7.4.0-rev14, in certain user-id sharing scenarios, does not properly construct a SQL statement for next-year birthdays, which allows remote authenticated users to obtain sensitive birthday, displayname, firstname, and surname information via a birthdays action to api/contacts, aka bug 29315.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Open-Xchange App Suite Backend	=7.2.0
Open-Xchange App Suite Backend	=7.2.1
Open-Xchange App Suite Backend	=7.2.2
Open-Xchange App Suite Backend	=7.4.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-6241?
CVE-2013-6241 has a high severity rating as it allows unauthorized access to sensitive birthday information.
How do I fix CVE-2013-6241?
To fix CVE-2013-6241, upgrade Open-Xchange App Suite to version 7.2.2-rev25 or later, or 7.4.0-rev14 or later.
Who is affected by CVE-2013-6241?
Users of Open-Xchange App Suite versions 7.2.0, 7.2.1, 7.2.2, and 7.4.0 are affected by CVE-2013-6241.
What kind of exploitation is possible with CVE-2013-6241?
CVE-2013-6241 can be exploited by remote authenticated users to access sensitive birthday data through improper SQL query construction.
Is there a workaround for CVE-2013-6241?
There is no official workaround for CVE-2013-6241; applying the latest patch is the recommended solution.

agent/references
agent/softwarecombine
agent/type
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/last-modified-date
agent/description
agent/author
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/open-xchange
canonical/open-xchange app suite backend
version/open-xchange app suite backend/7.2.0
version/open-xchange app suite backend/7.2.1
version/open-xchange app suite backend/7.2.2
version/open-xchange app suite backend/7.4.0

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.

Frequently Asked Questions

What is the severity of CVE-2013-6241?
CVE-2013-6241 has a high severity rating as it allows unauthorized access to sensitive birthday information.
How do I fix CVE-2013-6241?
To fix CVE-2013-6241, upgrade Open-Xchange App Suite to version 7.2.2-rev25 or later, or 7.4.0-rev14 or later.
Who is affected by CVE-2013-6241?
Users of Open-Xchange App Suite versions 7.2.0, 7.2.1, 7.2.2, and 7.4.0 are affected by CVE-2013-6241.
What kind of exploitation is possible with CVE-2013-6241?
CVE-2013-6241 can be exploited by remote authenticated users to access sensitive birthday data through improper SQL query construction.
Is there a workaround for CVE-2013-6241?
There is no official workaround for CVE-2013-6241; applying the latest patch is the recommended solution.