How severe is CVE-2003-1171?

CVE-2003-1171 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2003-1171 being actively exploited?

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

What products are affected by CVE-2003-1171?

CVE-2003-1171 primarily affects Mod Security. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2003-1171?

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-2003-1171 published?

CVE-2003-1171 was published on 2003-12-31 and last updated on 2026-06-16.

CVE-2003-1171

CVE-2003-1171 is a high-severity vulnerability in Mod Security 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: 5% (91st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Mod Security
Published: 2003-12-31
Last modified: 2026-06-16

Description

Heap-based buffer overflow in the sec_filter_out function in mod_security 1.7RC1 through 1.7.1 in Apache 2 allows remote attackers to execute arbitrary code via a server side script that sends a large amount of data.

Frequently asked questions

What is CVE-2003-1171?: Heap-based buffer overflow in the sec_filter_out function in mod_security 1.7RC1 through 1.7.1 in Apache 2 allows remote attackers to execute arbitrary code via a server side script that sends a large amount of data.
How severe is CVE-2003-1171?: CVE-2003-1171 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2003-1171 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2003-1171?: CVE-2003-1171 primarily affects Mod Security. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2003-1171?: 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-2003-1171 published?: CVE-2003-1171 was published on 2003-12-31 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:mod_security:mod_security:1.7:*:*:*:*:*:*:*
cpe:2.3:a:mod_security:mod_security:1.7.1:*:*:*:*:*:*:*

More vulnerabilities in Mod Security

CVE-2004-1765 — High (CVSS 7.5): Off-by-one buffer overflow in ModSecurity (mod_security) 1.7.4 for Apache 2.x, when SecFilterScanPost is enabled,…
CVE-2007-1359 — Medium (CVSS 6.8): Interpretation conflict in ModSecurity (mod_security) 2.1.0 and earlier allows remote attackers to bypass request rules…

All CVEs affecting Mod Security →