Menu

Star on GitHub · 3.2k

CVE-2005-4847

10.0 · HIGH

Unspecified vulnerability in Spey 0.3.3 has unknown impact and attack vectors related to "A number of security holes which could lead to compromise," a different issue than CVE-2005-4846.

Published Dec 31, 2005speyEPSS 1.24%

Overview

CVE-2005-4847 is a high-severity vulnerability affecting spey spey. It was published on December 31, 2005 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Unspecified vulnerability in Spey 0.3.3 has unknown impact and attack vectors related to "A number of security holes which could lead to compromise," a different issue than CVE-2005-4846.

Remediation

Check the references section for vendor advisories and patches from spey. Update spey to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2005-4847?

CVE-2005-4847 is a high-severity vulnerability affecting spey spey. It was published on December 31, 2005 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2005-4847?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-4847?

Check the references section for vendor advisories and patches from spey. Update spey to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2005-4847?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-4847 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2005

View all