What is the severity of CVE-2013-6789?

CVE-2013-6789 is considered a medium severity vulnerability as it can lead to disclosure of sensitive information.

How do I fix CVE-2013-6789?

To fix CVE-2013-6789, update to a version of SilverStripe that does not support credentials in a GET request.

Which versions of SilverStripe are affected by CVE-2013-6789?

CVE-2013-6789 specifically affects SilverStripe version 3.0.3.

What type of attacks does CVE-2013-6789 allow?

CVE-2013-6789 allows remote or local attackers to access sensitive information through web-server logs.

Is there a workaround for CVE-2013-6789 if I cannot update SilverStripe?

A potential workaround for CVE-2013-6789 is to avoid using GET requests for sensitive credential submissions.

Vulnerability/
CVE-2013-6789

medium

CWE

200

13/11/2013

17/9/2024

CVE-2013-6789: Infoleak

First published: Wed Nov 13 2013(Updated: )

security/MemberLoginForm.php in SilverStripe 3.0.3 supports credentials in a GET request, which allows remote or local attackers to obtain sensitive information by reading web-server access logs, web-server Referer logs, or the browser history, a similar vulnerability to CVE-2013-2653.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Silverstripe silverstripe	=3.0.3

Remedy

https://github.com/chillu/silverstripe-framework/commit/3e88c98ca513880e2b43ed7f27ade17fef5d9170

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-6789?
CVE-2013-6789 is considered a medium severity vulnerability as it can lead to disclosure of sensitive information.
How do I fix CVE-2013-6789?
To fix CVE-2013-6789, update to a version of SilverStripe that does not support credentials in a GET request.
Which versions of SilverStripe are affected by CVE-2013-6789?
CVE-2013-6789 specifically affects SilverStripe version 3.0.3.
What type of attacks does CVE-2013-6789 allow?
CVE-2013-6789 allows remote or local attackers to access sensitive information through web-server logs.
Is there a workaround for CVE-2013-6789 if I cannot update SilverStripe?
A potential workaround for CVE-2013-6789 is to avoid using GET requests for sensitive credential submissions.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/remedy
agent/weakness
agent/author
agent/severity
agent/tags
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
vendor/silverstripe
canonical/silverstripe silverstripe
version/silverstripe silverstripe/3.0.3

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-6789?
CVE-2013-6789 is considered a medium severity vulnerability as it can lead to disclosure of sensitive information.
How do I fix CVE-2013-6789?
To fix CVE-2013-6789, update to a version of SilverStripe that does not support credentials in a GET request.
Which versions of SilverStripe are affected by CVE-2013-6789?
CVE-2013-6789 specifically affects SilverStripe version 3.0.3.
What type of attacks does CVE-2013-6789 allow?
CVE-2013-6789 allows remote or local attackers to access sensitive information through web-server logs.
Is there a workaround for CVE-2013-6789 if I cannot update SilverStripe?
A potential workaround for CVE-2013-6789 is to avoid using GET requests for sensitive credential submissions.