How severe is CVE-2009-0545?

No CVSS score has been assigned to CVE-2009-0545 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2009-0545?

Affected package information for CVE-2009-0545 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2009-0545?

No fixed release is recorded for CVE-2009-0545 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2009-0545 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2009-0545 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2009-0545 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2009-0545, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2009-0545?

CVE-2009-0545 has an EPSS (Exploit Prediction Scoring System) score of 90.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2009-0545?

CVE-2009-0545 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2009-0545?

A Nuclei detection template exists for CVE-2009-0545, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2009-0545 published, and has it been updated?

CVE-2009-0545 was published on February 12, 2009 and was last updated on August 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2009-0545

CVE-2009-0545 is a Improper Input Validation vulnerability. 3 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

cgi-bin/kerbynet in ZeroShell 1.0beta11 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in the type parameter in a NoAuthREQ x509List action.

Published

Feb 12, 2009

Updated

Aug 7, 2024

Affected

1 product

Patched

See advisory

Exploits

3 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

90.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

cgi-bin/kerbynet in ZeroShell 1.0beta11 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in the type parameter in a NoAuthREQ x509List action.

Affected Products

1 product · 11 configurations

Application

zeroshellzeroshell

1 version

1.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-8023remotehardware✓ Verified

ZeroShell 1.0beta11 - Remote Code Execution

by ikki · Feb 9, 2009

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2009-0545 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2009-0545

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2009-0545 -u https://target

Template: ZeroShell <= 1.0beta11 Remote Code Execution
Severity: critical
Impact: Successful exploitation of this vulnerability allows remote attackers to execute arbitrary code on the affected system.
Remediation: Upgrade to a patched version of ZeroShell.

Template by ProjectDiscovery nuclei-templates (geeknik), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

cgi-bin/kerbynet in ZeroShell 1.0beta11 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in the type parameter in a NoAuthREQ x509List action.

O3 Security · Impact-Aware SCA

Is CVE-2009-0545 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2009-0545

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2009-0545

Frequently Asked Questions

Is CVE-2009-0545 in your dependencies?