What is the severity of CVE-2005-2517?

CVE-2005-2517 is classified as a moderate severity vulnerability that can lead to form data being sent to unintended destinations.

How do I fix CVE-2005-2517?

To fix CVE-2005-2517, users should update to a later version of Safari or upgrade their macOS to a version that mitigates this vulnerability.

What are the consequences of CVE-2005-2517?

The consequences of CVE-2005-2517 include potential data leakage as form submissions may be erroneously sent to malicious sites.

Which versions are affected by CVE-2005-2517?

CVE-2005-2517 affects Safari on Mac OS X versions 10.3.9 and 10.4.2.

Is there a way to detect CVE-2005-2517?

Detecting CVE-2005-2517 typically involves checking the version of Safari and ensuring it is not running on affected Mac OS X versions.

Vulnerability/
CVE-2005-2517

low

2.6

CWE

NVD-CWE-Other

19/8/2005

17/9/2024

CVE-2005-2517

First published: Fri Aug 19 2005(Updated: )

Safari in Mac OS X 10.3.9 and 10.4.2 submits forms from an XSL formatted page to the next page that is browsed by the user, which causes form data to be sent to the wrong site.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Apple Safari
macOS Yosemite	=10.3.9
macOS Yosemite	=10.4.2

Remedy

http://lists.apple.com/archives/security-announce/2005//Aug/msg00001.html

Remedy

http://lists.apple.com/archives/security-announce/2005/Aug/msg00000.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-2517?
CVE-2005-2517 is classified as a moderate severity vulnerability that can lead to form data being sent to unintended destinations.
How do I fix CVE-2005-2517?
To fix CVE-2005-2517, users should update to a later version of Safari or upgrade their macOS to a version that mitigates this vulnerability.
What are the consequences of CVE-2005-2517?
The consequences of CVE-2005-2517 include potential data leakage as form submissions may be erroneously sent to malicious sites.
Which versions are affected by CVE-2005-2517?
CVE-2005-2517 affects Safari on Mac OS X versions 10.3.9 and 10.4.2.
Is there a way to detect CVE-2005-2517?
Detecting CVE-2005-2517 typically involves checking the version of Safari and ensuring it is not running on affected Mac OS X versions.

agent/references
agent/first-publish-date
agent/remedy
agent/type
agent/severity
agent/weakness
agent/author
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
agent/softwarecombine
vendor/apple
canonical/apple safari
canonical/macos yosemite
version/macos yosemite/10.3.9
version/macos yosemite/10.4.2

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-2005-2517?
CVE-2005-2517 is classified as a moderate severity vulnerability that can lead to form data being sent to unintended destinations.
How do I fix CVE-2005-2517?
To fix CVE-2005-2517, users should update to a later version of Safari or upgrade their macOS to a version that mitigates this vulnerability.
What are the consequences of CVE-2005-2517?
The consequences of CVE-2005-2517 include potential data leakage as form submissions may be erroneously sent to malicious sites.
Which versions are affected by CVE-2005-2517?
CVE-2005-2517 affects Safari on Mac OS X versions 10.3.9 and 10.4.2.
Is there a way to detect CVE-2005-2517?
Detecting CVE-2005-2517 typically involves checking the version of Safari and ensuring it is not running on affected Mac OS X versions.