Vulnerability in chromium-browser: Multiple Security Issues

chromium-browser Updated 02 Oct 2025

Summary

16/02/2014
N/A
Yes i
Unrated
Not published

DSA-2862-1: chromium-browser - several. Affects chromium-browser versions < 32.0.1700.123-1~deb7u1. Fixed in 32.0.1700.123-1~deb7u1. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The chromium-browser is a popular web browser developed by Google. It is based on the open-source Chromium project and provides a fast and secure browsing experience. The browser is widely used across different platforms and is known for its robust features and frequent updates. However, several vulnerabilities have been discovered in the chromium-browser, which could potentially compromise user security and privacy.

Vulnerability Detail

The discovered vulnerabilities in the chromium-browser include:

  1. Use-after-free issue in Blink/Webkit form elements (CVE-2013-6641): This vulnerability could allow an attacker to execute arbitrary code by manipulating form elements.

  2. Google account information disclosure issue related to one-click sign-on feature (CVE-2013-6643): This vulnerability could lead to the unauthorized disclosure of user account information.

  3. Multiple issues with potential security impact (CVE-2013-6644): The chrome development team discovered and fixed various security issues that could potentially be exploited by attackers.

  4. Use-after-free issue related to speech input (CVE-2013-6645): This vulnerability could allow an attacker to execute arbitrary code by exploiting speech input functionality.

  5. Use-after-free issue in web workers implementation (CVE-2013-6646): This vulnerability could lead to the execution of arbitrary code by manipulating web workers.

  6. Use-after-free issue in Blink/Webkit SVG implementation (CVE-2013-6649): This vulnerability could allow an attacker to execute arbitrary code by manipulating SVG elements.

  7. Memory corruption in the v8 JavaScript library (CVE-2013-6650): This vulnerability could lead to the execution of arbitrary code by exploiting memory corruption in the JavaScript engine.

These vulnerabilities pose a significant risk to users of the chromium-browser, as they could potentially be exploited by malicious individuals to gain unauthorized access to sensitive information or execute arbitrary code.

How To Fix

Minimum fixed version

32.0.1700.123-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

The discovered vulnerabilities in the chromium-browser pose a significant risk to user security and privacy. It is crucial for users to update their chromium-browser installations to the latest version (32.0.1700.123-1~deb7u1 or later) to mitigate these risks. Failure to update could leave systems vulnerable to potential attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for chromium-browser →

Share this vulnerability

FAQ

To check the version of your chromium-browser, open the browser and go to the 'About Chromium' or 'About Chrome' section. This will display the current version number.

No, the recommended approach is to update the chromium-browser to the latest version provided by the official distribution repositories. This ensures that all necessary security patches and fixes are applied correctly.

At the moment, there are no known workarounds for these vulnerabilities. It is crucial to update the chromium-browser to the latest version to mitigate the risks.

Yes, these vulnerabilities can be exploited remotely. Attackers can craft malicious websites or content that, when accessed by a user using an outdated version of the chromium-browser, can trigger the vulnerabilities and potentially compromise the user's system.

There have been reports of active exploitation of some of these vulnerabilities in the wild. It is essential to update the chromium-browser to the latest version to protect against potential attacks.

Related vulnerabilities

Recent vulnerabilities recorded for chromium-browser.

How To Fix

Minimum fixed version

32.0.1700.123-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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback