What is the severity of CVE-2007-0614?

CVE-2007-0614 is classified as a denial of service vulnerability that can cause persistent application crashes.

How do I fix CVE-2007-0614?

To mitigate the effects of CVE-2007-0614, it is recommended to update to the latest version of macOS and affected applications if available.

Which software is affected by CVE-2007-0614?

CVE-2007-0614 affects Apple iChat version 3.1.6, the Instant Message framework version 428, and macOS X version 10.4.8.

What can attackers achieve with CVE-2007-0614?

Attackers can exploit CVE-2007-0614 to crash applications utilizing the Bonjour functionality, resulting in a denial of service.

Is there a workaround for CVE-2007-0614?

Currently, the best approach for CVE-2007-0614 is to avoid using the affected software or restrict access to untrusted networks.

Vulnerability/
CVE-2007-0614

high

7.8

CWE

NVD-CWE-Other

31/1/2007

7/8/2024

CVE-2007-0614

First published: Wed Jan 31 2007(Updated: )

The Bonjour functionality in mDNSResponder, iChat 3.1.6, and InstantMessage framework 428 in Apple Mac OS X 10.4.8 allows remote attackers to cause a denial of service (persistent application crash) via a crafted phsh hash attribute in a TXT key.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Apple iChat	=3.1.6
Apple Instant Message framework	=428
macOS Yosemite	=10.4.8

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-0614?
CVE-2007-0614 is classified as a denial of service vulnerability that can cause persistent application crashes.
How do I fix CVE-2007-0614?
To mitigate the effects of CVE-2007-0614, it is recommended to update to the latest version of macOS and affected applications if available.
Which software is affected by CVE-2007-0614?
CVE-2007-0614 affects Apple iChat version 3.1.6, the Instant Message framework version 428, and macOS X version 10.4.8.
What can attackers achieve with CVE-2007-0614?
Attackers can exploit CVE-2007-0614 to crash applications utilizing the Bonjour functionality, resulting in a denial of service.
Is there a workaround for CVE-2007-0614?
Currently, the best approach for CVE-2007-0614 is to avoid using the affected software or restrict access to untrusted networks.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/author
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/apple
canonical/apple ichat server
version/apple ichat server/3.1.6
canonical/apple instant message framework
version/apple instant message framework/428
canonical/apple ios and macos
version/apple ios and macos/10.4.8

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-2007-0614?
CVE-2007-0614 is classified as a denial of service vulnerability that can cause persistent application crashes.
How do I fix CVE-2007-0614?
To mitigate the effects of CVE-2007-0614, it is recommended to update to the latest version of macOS and affected applications if available.
Which software is affected by CVE-2007-0614?
CVE-2007-0614 affects Apple iChat version 3.1.6, the Instant Message framework version 428, and macOS X version 10.4.8.
What can attackers achieve with CVE-2007-0614?
Attackers can exploit CVE-2007-0614 to crash applications utilizing the Bonjour functionality, resulting in a denial of service.
Is there a workaround for CVE-2007-0614?
Currently, the best approach for CVE-2007-0614 is to avoid using the affected software or restrict access to untrusted networks.