CVE-2005-4155
published 2005-12-11CVE-2005-4155: registration.PHP in ATutor 1.5.1 pl2 allows remote attackers to execute arbitrary SQL commands via an e-mail address that ends in a NULL character, which…
PriorityP339high7.5CVSS 2.0
AVNACLAuNCPIPAP
EXPLOIT
EPSS
2.68%
83.9th percentile
registration.PHP in ATutor 1.5.1 pl2 allows remote attackers to execute arbitrary SQL commands via an e-mail address that ends in a NULL character, which bypasses the PHP regular expression check. NOTE: it is possible that this is actually a bug in PHP code, in which case this should not be treated as a vulnerability in ATutor.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| adaptive_technology_resource_centre | atutor | — | — |
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No writeups or analysis indexed.
CWE
Improper Neutralization of Null Byte or NUL Character
mitre_cwe
CWE-158 Improper Neutralization of Null Byte or NUL Character
CWE-158: Improper Neutralization of Null Byte or NUL Character
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.
As data is parsed, an injected NUL character or null byte may cause the product to believe the input is terminated earlier than it actually is, or otherwise cause the input to be misinterpreted. This could then be used to inject potentially dangerous input that occurs after the null byte or otherwise bypass validation routines and other protection mechanisms.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity. Impact: Unexpected State.
Potential Mitigations:
Developers should anticipate that null characters or
CWE
Incorrect Regular Expression
mitre_cwe
CWE-185 Incorrect Regular Expression
CWE-185: Incorrect Regular Expression
The product specifies a regular expression in a way that causes data to be improperly matched or compared.
When the regular expression is used in protection mechanisms such as filtering or validation, this may allow an attacker to bypass the intended restrictions on the incoming data.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Unexpected State, Varies by Context. When the regular expression is not correctly specified, data might have a different format or type than the rest of the program expects, producing resultant weaknesses or errors.
Scope: Access Control. Impact: Bypass Protection Mechanism. In PHP, regular expression checks can sometimes be bypassed with a null byte, leading to any number of weakn
CWE
Null Byte Interaction Error (Poison Null Byte)
mitre_cwe·CVSS 7.5
[HIGH] CWE-626 Null Byte Interaction Error (Poison Null Byte)
CWE-626: Null Byte Interaction Error (Poison Null Byte)
The product does not properly handle null bytes or NUL characters when passing data between different representations or components.
A null byte (NUL character) can have different meanings across representations or languages. For example, it is a string terminator in standard C libraries, but Perl and PHP strings do not treat it as a terminator. When two representations are crossed - such as when Perl or PHP invokes underlying C functionality - this can produce an interaction error with unexpected results. Similar issues have been reported for ASP. Other interpreters written in C might also be affected. The poison null byte is frequently useful in path traversal attacks by terminating hard-coded extensions that are added to a filena
http://rgod.altervista.org/atutor151pl2.htmlhttp://securitytracker.com/alerts/2005/Nov/1015166.htmlhttp://www.osvdb.org/20851http://www.securityfocus.com/bid/15355/http://rgod.altervista.org/atutor151pl2.htmlhttp://securitytracker.com/alerts/2005/Nov/1015166.htmlhttp://www.osvdb.org/20851http://www.securityfocus.com/bid/15355/
2005-12-11
Published