CVE-2005-4847: Unspecified vulnerability in Spey 0.3.3 has unknown impact and attack vectors related to "A number of security

This month

HIGH 10.0DOWNGRADE

CVE-2005-4847 is a high-severity flaw (CVSS 10.0) affecting spey. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Published	2005-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: spey

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:19 UTCUpdated Record last modified

spey spey DOWNGRADE

Affected: 0.3.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.3.3

1. Check installed version

apt-cache policy spey || rpm -q spey || spey --version

2. No fixed release: DOWNGRADE to a release before 0.3.3 (Debian / Ubuntu)

apt-cache madison spey sudo apt install spey=<VERSION_BEFORE_0.3.3> sudo apt-mark hold spey

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spey sudo dnf downgrade spey-<VERSION_BEFORE_0.3.3> sudo dnf versionlock add spey

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-4847?

spey: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-4847 being exploited?

CVE-2005-4847 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-4847 affect?

CVE-2005-4847 affects spey. Severity is high (CVSS 10.0). 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.

How urgent is CVE-2005-4847?

Priority 52/100. Critical severity

Related CVEs

CVE-2007-3298 HIGH 7.5 UPGRADE SQL injection vulnerability in Spey before 0.4.1 allows remote attackers to execute arbitrary SQL commands via
CVE-2005-4846 MEDIUM 4.3 DOWNGRADE Format string vulnerability in Logger.cc for Spey 0.3.3 allows attackers to cause a denial of service (crash)

References

← Back to latest CVEs