How severe is CVE-2005-3008?

CVE-2005-3008 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2005-3008 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-3008?

CVE-2005-3008 affects Amar Sagoo Tofu. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2005-3008?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2005-3008 published?

CVE-2005-3008 was published on 2005-09-21 and last updated on 2026-06-16.

CVE-2005-3008

CVE-2005-3008 is a high-severity vulnerability in Amar Sagoo Tofu with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 2% (72nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Amar Sagoo Tofu
Published: 2005-09-21
Last modified: 2026-06-16

Description

Tofu 0.2 allows remote attackers to execute arbitrary Python code via crafted pickled objects, which Tofu unpickles and executes.

Frequently asked questions

What is CVE-2005-3008?: Tofu 0.2 allows remote attackers to execute arbitrary Python code via crafted pickled objects, which Tofu unpickles and executes.
How severe is CVE-2005-3008?: CVE-2005-3008 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-3008 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-3008?: CVE-2005-3008 affects Amar Sagoo Tofu. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2005-3008?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2005-3008 published?: CVE-2005-3008 was published on 2005-09-21 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:amar_sagoo:tofu:0.2:*:*:*:*:*:*:*