Vulnerability in chromium-browser package

chromium-browser Updated 02 Oct 2025

Summary

16/11/2013
N/A
Yes i
Unrated
Not published

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 ↓

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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

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:

  1. CVE-2013-2931: Various issues found through internal fuzzing, audits, and other studies.
  2. CVE-2013-6621: Use-after-free issue in speech input handling.
  3. CVE-2013-6622: Use-after-free issue in HTMLMediaElement.
  4. CVE-2013-6623: Out-of-bounds read in the Blink/Webkit SVG implementation.
  5. CVE-2013-6624: Use-after-free issue in id attribute strings.
  6. CVE-2013-6625: Use-after-free issue in the Blink/Webkit DOM implementation.
  7. CVE-2013-6626: Address bar spoofing issue.
  8. CVE-2013-6627: Out-of-bounds read in the HTTP stream parser.
  9. CVE-2013-6628: TLS renegotiation vulnerability allowing the use of a different certificate.
  10. CVE-2013-6629: Uninitialized memory read in the libjpeg and libjpeg-turbo libraries.
  11. CVE-2013-6630: Another uninitialized memory read in the libjpeg and libjpeg-turbo libraries.
  12. CVE-2013-6631: Use-after-free issue in the libjingle library.
  13. 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 →

Share this vulnerability

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.

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 →

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