Bug 670806 (CVE-2010-4699)
| Summary: | CVE-2010-4699 php: iconv_mime_decode_headers skips headers using unsupported encoding | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Tomas Hoger <thoger> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | jorton |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-01-20 21:01:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tomas Hoger
2011-01-19 12:58:53 UTC
This looks more like regular bug / enhancement rather than security flaw. Upstream did not consider this to be security fix, security impacts mentioned the CVE description are fairly vague. Checking with the upstream SVN test case, this bug occurs when iconv_mime_decode_headers is called with ICONV_MIME_DECODE_CONTINUE_ON_ERROR flag, i.e. when it's asked to continue parsing headers even when some error was detected. So it's asked to perform a best effort recovery for the malformed input. When called without this flag set, iconv_mime_decode_headers returns false. Fixing the code that tries to recover form errors is a bug fix, but it does not seem to qualify as a security fix. Joe, do you possibly see what I may be missing? No, I don't see any security issue there, I presume it is extrapolated from "skipping spam checks". Even upstream didn't list this under the security fixes in the 5.3.4 changes. Statement: Red Hat does not consider this issue to be a security vulnerability, rather consider this to be a non-security bug. |