What is the severity of CVE-2012-4001?

CVE-2012-4001 is classified as a moderate severity vulnerability due to its potential to allow remote attackers to perform unauthorized HTTP requests.

How do I fix CVE-2012-4001?

To fix CVE-2012-4001, upgrade the mod_pagespeed module to version 0.10.22.6 or later.

What software versions are affected by CVE-2012-4001?

CVE-2012-4001 affects mod_pagespeed versions up to 0.10.22.4 and the specific version 0.10.19.1.

Can CVE-2012-4001 allow access to intranet servers?

Yes, CVE-2012-4001 can be exploited to send HTTP requests to intranet servers, posing a security risk.

Is the Apache HTTP Server vulnerable in CVE-2012-4001?

The Apache HTTP Server itself is not directly vulnerable; the issue lies within the mod_pagespeed module.

Vulnerability/
CVE-2012-4001

medium

CWE

15/9/2012

17/9/2024

CVE-2012-4001: Input Validation

First published: Sat Sep 15 2012(Updated: )

The mod_pagespeed module before 0.10.22.6 for the Apache HTTP Server does not properly verify its host name, which allows remote attackers to trigger HTTP requests to arbitrary hosts via unspecified vectors, as demonstrated by requests to intranet servers.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Google Mod Pagespeed	<=0.10.22.4
Google Mod Pagespeed	=0.10.19.1
Apache HTTP Server

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2012-4001?
CVE-2012-4001 is classified as a moderate severity vulnerability due to its potential to allow remote attackers to perform unauthorized HTTP requests.
How do I fix CVE-2012-4001?
To fix CVE-2012-4001, upgrade the mod_pagespeed module to version 0.10.22.6 or later.
What software versions are affected by CVE-2012-4001?
CVE-2012-4001 affects mod_pagespeed versions up to 0.10.22.4 and the specific version 0.10.19.1.
Can CVE-2012-4001 allow access to intranet servers?
Yes, CVE-2012-4001 can be exploited to send HTTP requests to intranet servers, posing a security risk.
Is the Apache HTTP Server vulnerable in CVE-2012-4001?
The Apache HTTP Server itself is not directly vulnerable; the issue lies within the mod_pagespeed module.

agent/references
agent/type
agent/severity
agent/author
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
agent/source
vendor/google
canonical/google mod pagespeed
version/google mod pagespeed/0.10.22.4
version/google mod pagespeed/0.10.19.1
vendor/apache
canonical/apache http server

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-2012-4001?
CVE-2012-4001 is classified as a moderate severity vulnerability due to its potential to allow remote attackers to perform unauthorized HTTP requests.
How do I fix CVE-2012-4001?
To fix CVE-2012-4001, upgrade the mod_pagespeed module to version 0.10.22.6 or later.
What software versions are affected by CVE-2012-4001?
CVE-2012-4001 affects mod_pagespeed versions up to 0.10.22.4 and the specific version 0.10.19.1.
Can CVE-2012-4001 allow access to intranet servers?
Yes, CVE-2012-4001 can be exploited to send HTTP requests to intranet servers, posing a security risk.
Is the Apache HTTP Server vulnerable in CVE-2012-4001?
The Apache HTTP Server itself is not directly vulnerable; the issue lies within the mod_pagespeed module.