CVE-2015-6783
chromium-browser: Signature validation issue in Android Crazy Linker
Overview
Description
The FindStartOffsetOfFileInZipFile function in crazy_linker_zip.cpp in crazy_linker (aka Crazy Linker) in Android 5.x and 6.x, as used in Google Chrome before 47.0.2526.73, improperly searches for an EOCD record, which allows attackers to bypass a signature-validation requirement via a crafted ZIP archive.
Source: OX vulnerability database
Severity
6.4 · MEDIUM
CVSS 2.0 base score, scored by redhat.
- Access vector
- Network
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
Weakness: CWE-20
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 2 fixes
openSUSE 1 release · 2 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | ungoogled-chromium +1 | 113.0.5672.92-1.1 | openSUSE-SU-2024:12948-1 |
| Tumbleweed | chromedriver +1 | 55.0.2883.75-3.1 | openSUSE-SU-2024:10171-1 |
References
- googlechromereleases.blogspot.com http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00016.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00017.html
- www.securityfocus.com http://www.securityfocus.com/bid/78416
- www.securitytracker.com http://www.securitytracker.com/id/1034298
- access.redhat.com https://access.redhat.com/security/cve/CVE-2015-6783
- chromium.googlesource.com https://chromium.googlesource.com/chromium/src.git/+/d9e316238aee59acf665d80b544cf4e1edfd3349
- code.google.com https://code.google.com/p/chromium/issues/detail?id=537205
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2015-6783
- security.gentoo.org https://security.gentoo.org/glsa/201603-09
Show all 11 references
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.