CWE-145
Weakness AllowedImproper Neutralization of Section Delimiters
Abstraction: Variant · Status: Incomplete
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as section delimiters when they are sent to a downstream component.
Technical nuance
One example of a section delimiter is the boundary string in a multipart MIME message. In many cases, doubled line delimiters can serve as a section delimiter.
Mapping guidance
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
Notes
Relationship
Depending on the language and syntax being used, this could be the same as the record delimiter (CWE-143).
Content history
updated Potential_Mitigations, Time_of_Introduction
updated Relationships, Relationship_Notes, Taxonomy_Mappings
updated Description
updated Potential_Mitigations
updated Description, Name
updated Description
updated Potential_Mitigations
updated Common_Consequences
updated Common_Consequences
updated References, Relationships
updated Potential_Mitigations
updated Relationships, Taxonomy_Mappings
updated Potential_Mitigations
updated Applicable_Platforms
updated Potential_Mitigations, Relationships
updated Potential_Mitigations
updated Description, Potential_Mitigations
updated Relationships
updated Mapping_Notes
updated Weakness_Ordinalities
updated Common_Consequences, Description, Technical_Nuance
2 vulnerabilities reference this CWE, most recent first.
CVE-2011-10043 (GCVE-0-2011-10043)
Vulnerability from cvelistv5 – Published: 2026-07-07 11:46 – Updated: 2026-07-07 16:04- CWE-145 - Improper Neutralization of Section Delimiters
| URL | Tags |
|---|---|
| https://blogs.perl.org/users/michael_g_schwern/20… | technical-description |
| https://metacpan.org/release/BINGOS/Module-Load-0… | |
| https://metacpan.org/release/BINGOS/Module-Load-0… | release-notes |
| Vendor | Product | Version | |
|---|---|---|---|
| BINGOS | Module::Load |
Affected:
0 , < 0.22
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2011-10043",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-07T16:04:25.108284Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-07-07T16:04:29.197Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://cpan.org/modules",
"defaultStatus": "unaffected",
"packageName": "Module-Load",
"product": "Module::Load",
"programFiles": [
"lib/Module/Load.pm"
],
"programRoutines": [
{
"name": "Module::Load::_to_file"
}
],
"repo": "https://github.com/jib/module-load",
"vendor": "BINGOS",
"versions": [
{
"lessThan": "0.22",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Module::Load versions before 0.22 for Perl allow arbitrary modules outside of @INC to be loaded.\n\nModule names starting with \"::\" could be passed to the load function to specify arbitrary module paths.\n\nAttackers able to influence module names passed to load could use that bug to execute arbitrary code."
}
],
"impacts": [
{
"capecId": "CAPEC-242",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-242 Code Injection"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-145",
"description": "CWE-145 Improper Neutralization of Section Delimiters",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-07-07T11:46:13.575Z",
"orgId": "9b29abf9-4ab0-4765-b253-1875cd9b441e",
"shortName": "CPANSec"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://blogs.perl.org/users/michael_g_schwern/2011/10/how-not-to-load-a-module-or-bad-interfaces-make-good-people-do-bad-things.html"
},
{
"url": "https://metacpan.org/release/BINGOS/Module-Load-0.22/diff/BINGOS/Module-Load-0.20/lib/Module/Load.pm"
},
{
"tags": [
"release-notes"
],
"url": "https://metacpan.org/release/BINGOS/Module-Load-0.22/changes"
}
],
"solutions": [
{
"lang": "en",
"value": "If you are using Perl v5.15.3 or earlier, then upgrade to Module::Load 0.22 or later.\n\nPerl versions after v5.15.4 include newer versions of Module::Load that fix this issue."
}
],
"source": {
"discovery": "UNKNOWN"
},
"timeline": [
{
"lang": "en",
"time": "2011-10-02T00:00:00.000Z",
"value": "General issue identified by Michael G Schwern in blog post."
},
{
"lang": "en",
"time": "2011-10-04T00:00:00.000Z",
"value": "Module::Load 0.22 released."
},
{
"lang": "en",
"time": "2011-10-20T00:00:00.000Z",
"value": "Perl v5.15.4 released with Module::Load 0.22."
}
],
"title": "Module::Load versions before 0.22 for Perl allow arbitrary modules outside of @INC to be loaded",
"x_generator": {
"engine": "cpansec-cna-tool 0.1"
}
}
},
"cveMetadata": {
"assignerOrgId": "9b29abf9-4ab0-4765-b253-1875cd9b441e",
"assignerShortName": "CPANSec",
"cveId": "CVE-2011-10043",
"datePublished": "2026-07-07T11:46:13.575Z",
"dateReserved": "2026-07-05T11:47:35.949Z",
"dateUpdated": "2026-07-07T16:04:29.197Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GHSA-8X3H-9QCG-HV3J
Vulnerability from github – Published: 2026-07-07 12:31 – Updated: 2026-07-07 18:30Module::Load versions before 0.22 for Perl allow arbitrary modules outside of @INC to be loaded.
Module names starting with "::" could be passed to the load function to specify arbitrary module paths.
Attackers able to influence module names passed to load could use that bug to execute arbitrary code.
{
"affected": [],
"aliases": [
"CVE-2011-10043"
],
"database_specific": {
"cwe_ids": [
"CWE-145"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-07T12:16:24Z",
"severity": "CRITICAL"
},
"details": "Module::Load versions before 0.22 for Perl allow arbitrary modules outside of @INC to be loaded.\n\nModule names starting with \"::\" could be passed to the load function to specify arbitrary module paths.\n\nAttackers able to influence module names passed to load could use that bug to execute arbitrary code.",
"id": "GHSA-8x3h-9qcg-hv3j",
"modified": "2026-07-07T18:30:41Z",
"published": "2026-07-07T12:31:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-10043"
},
{
"type": "WEB",
"url": "https://blogs.perl.org/users/michael_g_schwern/2011/10/how-not-to-load-a-module-or-bad-interfaces-make-good-people-do-bad-things.html"
},
{
"type": "WEB",
"url": "https://metacpan.org/release/BINGOS/Module-Load-0.22/changes"
},
{
"type": "WEB",
"url": "https://metacpan.org/release/BINGOS/Module-Load-0.22/diff/BINGOS/Module-Load-0.20/lib/Module/Load.pm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
Developers should anticipate that section delimiters will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.
Mitigation MIT-5
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
Mitigation MIT-28
Strategy: Output Encoding
While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).
Mitigation MIT-20
Strategy: Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
No CAPEC attack patterns related to this CWE.