Vulnerability in chromium-browser package
Summary
DSA-2799-1: chromium-browser - several. Affects chromium-browser versions < 31.0.1650.57-1~deb7u1. Fixed in 31.0.1650.57-1~deb7u1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The chromium-browser package is a web browser developed by the Chrome 31 development team. It is widely used for browsing the internet and offers various features and functionalities. However, several vulnerabilities have been discovered in this package, which could potentially lead to security breaches and unauthorized access to user data.
Vulnerability Detail
The discovered vulnerabilities in the chromium-browser package include:
- CVE-2013-2931: Various issues found through internal fuzzing, audits, and other studies.
- CVE-2013-6621: Use-after-free issue in speech input handling.
- CVE-2013-6622: Use-after-free issue in HTMLMediaElement.
- CVE-2013-6623: Out-of-bounds read in the Blink/Webkit SVG implementation.
- CVE-2013-6624: Use-after-free issue in id attribute strings.
- CVE-2013-6625: Use-after-free issue in the Blink/Webkit DOM implementation.
- CVE-2013-6626: Address bar spoofing issue.
- CVE-2013-6627: Out-of-bounds read in the HTTP stream parser.
- CVE-2013-6628: TLS renegotiation vulnerability allowing the use of a different certificate.
- CVE-2013-6629: Uninitialized memory read in the libjpeg and libjpeg-turbo libraries.
- CVE-2013-6630: Another uninitialized memory read in the libjpeg and libjpeg-turbo libraries.
- CVE-2013-6631: Use-after-free issue in the libjingle library.
- CVE-2013-6632: Multiple memory corruption issues.
These vulnerabilities can potentially be exploited by attackers to execute arbitrary code, bypass security restrictions, or obtain sensitive information.
How To Fix
Minimum fixed version
31.0.1650.57-1~deb7u1
This is the first release that contains the fix.
sudo apt-get install --only-upgrade chromium-browser
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
Upgrading to the latest version of the chromium-browser package is crucial to mitigate the risks associated with these vulnerabilities. It is recommended to promptly update the package to ensure the security of your system and protect against potential attacks. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for chromium-browser →
FAQ
The chromium-browser package is a web browser developed by the Chrome 31 development team.
These vulnerabilities can potentially be exploited by attackers to execute arbitrary code, bypass security restrictions, or obtain sensitive information.
To fix the vulnerabilities, it is recommended to upgrade to the latest version of the chromium-browser package.
No specific workarounds have been mentioned for these vulnerabilities.
You can find more information about these vulnerabilities in the provided CVE links.
Related vulnerabilities
Recent vulnerabilities recorded for chromium-browser.