Mod Security
Approved changes feed: RSS · Atom
cpe:2.3:a:mod_security:mod_security:1.7.2:*:*:*:*:*:*:*part: a version: 1.7.2 update: *
| Vendor | Mod Security (1fb630d2-1c2d-53f6-81ca-e31be05abf5f) |
|---|---|
| Product | Mod Security (52d7d129-7b44-5ace-8302-3180d1a9968a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2007-1359 |
vulnerable | 2026-06-08 04:49:42.223320 |
Details available
Interpretation conflict in ModSecurity (mod_security) 2.1.0 and earlier allows remote attackers to bypass request rules via application/x-www-form-urlencoded POST data that contains an ASCIIZ (0x00) byte, which mod_security treats as a terminator even though it is still processed as normal data by some HTTP parsers including PHP 5.2.0, and possibly parsers in Perl, and Python.
Published: 2007-03-08T17:00:00.000Z
Updated: 2024-08-07T12:50:35.501Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.