Vulnerabilities in chromium-browser

chromium-browser Updated 02 Oct 2025

Summary

26/10/2013
N/A
Yes i
Unrated
Not published

DSA-2785-1: chromium-browser - several. Affects chromium-browser versions < 30.0.1599.101-1~deb7u1. Fixed in 30.0.1599.101-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The chromium-browser is a web browser developed by the Chromium project. It is an open-source browser that serves as the foundation for many popular browsers, including Google Chrome. The browser provides users with a fast and secure browsing experience, leveraging the latest web technologies. However, several vulnerabilities have been discovered in the chromium-browser, which could potentially be exploited by attackers to compromise user systems or steal sensitive information.

Vulnerability Detail

The chromium-browser is affected by multiple vulnerabilities, including race conditions, out-of-bounds reads, address bar spoofing, use-after-free issues, and memory corruption. These vulnerabilities have been discovered by various researchers and security teams. Exploiting these vulnerabilities could lead to arbitrary code execution, information disclosure, or denial of service. The specific technical details of each vulnerability can be found in the related CVEs mentioned in the vulnerability details.

How To Fix

Minimum fixed version

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

Workaround

There are no specific workarounds mentioned for these vulnerabilities. However, users can mitigate the risk by ensuring they have the latest version of the chromium-browser installed and by practicing safe browsing habits, such as avoiding suspicious websites and not clicking on unknown links.

Conclusion

The chromium-browser is prone to multiple vulnerabilities that could be exploited by attackers. It is crucial for users to update their chromium-browser packages to the latest version to ensure they are protected against these vulnerabilities. Additionally, practicing safe browsing habits and regularly checking for updates can help mitigate the risk. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for chromium-browser →

Share this vulnerability

FAQ

These vulnerabilities could allow attackers to execute arbitrary code, disclose sensitive information, or cause denial of service on systems running the chromium-browser.

The vulnerabilities have been fixed in version 30.0.1599.101-1~deb7u1 for the stable distribution (wheezy) and version 30.0.1599.101-1 for the unstable distribution (sid). The fixes for the testing distribution (jessie) will be available soon.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by these vulnerabilities. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.

There are no specific workarounds mentioned for these vulnerabilities. However, keeping your chromium-browser up to date and practicing safe browsing habits can help mitigate the risk.

For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing these vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for chromium-browser.

How To Fix

Minimum fixed version

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