What is the severity of CVE-2010-2791?

CVE-2010-2791 is considered a medium severity vulnerability due to its potential to expose sensitive information.

How do I fix CVE-2010-2791?

To fix CVE-2010-2791, upgrade the Apache HTTP Server to version 2.2.10 or later.

Which versions of Apache HTTP Server are affected by CVE-2010-2791?

CVE-2010-2791 affects Apache HTTP Server version 2.2.9 when running on Unix.

Can CVE-2010-2791 be exploited remotely?

Yes, CVE-2010-2791 can be exploited remotely by attackers to retrieve sensitive information.

What does CVE-2010-2791 involve regarding backend connections?

CVE-2010-2791 involves an issue where mod_proxy does not close the backend connection after a timeout occurs, leading to possible information leakage.

Vulnerability/
CVE-2010-2791

medium

CWE

200

5/8/2010

7/11/2023

CVE-2010-2791: Infoleak

First published: Thu Aug 05 2010(Updated: )

mod_proxy in httpd in Apache HTTP Server 2.2.9, when running on Unix, does not close the backend connection if a timeout occurs when reading a response from a persistent connection, which allows remote attackers to obtain a potentially sensitive response intended for a different client in opportunistic circumstances via a normal HTTP request. NOTE: this is the same issue as CVE-2010-2068, but for a different OS and set of affected versions.

Credit: secalert@redhat.com secalert@redhat.com

Affected Software	Affected Version	How to fix
Apache HTTP Server	=2.2.9
UNIX UNIX

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2010-2791?
CVE-2010-2791 is considered a medium severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2010-2791?
To fix CVE-2010-2791, upgrade the Apache HTTP Server to version 2.2.10 or later.
Which versions of Apache HTTP Server are affected by CVE-2010-2791?
CVE-2010-2791 affects Apache HTTP Server version 2.2.9 when running on Unix.
Can CVE-2010-2791 be exploited remotely?
Yes, CVE-2010-2791 can be exploited remotely by attackers to retrieve sensitive information.
What does CVE-2010-2791 involve regarding backend connections?
CVE-2010-2791 involves an issue where mod_proxy does not close the backend connection after a timeout occurs, leading to possible information leakage.

collector/nvd-historical
agent/severity
agent/author
agent/type
agent/event
agent/weakness
agent/last-modified-date
agent/first-publish-date
agent/tags
collector/nvd-api
agent/software-canonical-lookup-request
collector/nvd-index
agent/references
agent/description
agent/softwarecombine
vendor/apache
canonical/apache http server
version/apache http server/2.2.9
vendor/unix
canonical/unix unix

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-2010-2791?
CVE-2010-2791 is considered a medium severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2010-2791?
To fix CVE-2010-2791, upgrade the Apache HTTP Server to version 2.2.10 or later.
Which versions of Apache HTTP Server are affected by CVE-2010-2791?
CVE-2010-2791 affects Apache HTTP Server version 2.2.9 when running on Unix.
Can CVE-2010-2791 be exploited remotely?
Yes, CVE-2010-2791 can be exploited remotely by attackers to retrieve sensitive information.
What does CVE-2010-2791 involve regarding backend connections?
CVE-2010-2791 involves an issue where mod_proxy does not close the backend connection after a timeout occurs, leading to possible information leakage.