Vulnerability in Brave Software Inc. Brave (CVE-2018-1000815)

Summary

Vulnerability in Brave Software Inc. Brave (CVE-2018-1000815). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.25.2 or later.

Original description

The description as published by the source.

Brave Software Inc. Brave version version 0.22.810 to 0.24.0 contains a Other/Unknown vulnerability in function ContentSettingsObserver::AllowScript() in content_settings_observer.cc that can result in Websites can run inline JavaScript even if script is blocked, making attackers easier to track users. This attack appear to be exploitable via the victim must visit a specially crafted website. This vulnerability appears to have been fixed in 0.25.2.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2018-1000815 has been found in Brave Software Inc. Brave.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Brave Software Inc. Brave to 0.25.2 or later.
If unsure, ask your IT team or search "Brave Software Inc. Brave CVE-2018-1000815" on the vendor's site.

CVE-2018-1000815 (Brave Software Inc. Brave)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.25.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Brave Software Inc. Brave.

📍 Affected scope

Check the vendor advisory for the affected versions of Brave Software Inc. Brave.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.25.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Brave Software Inc. Brave を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade Brave Software Inc. Brave to 0.25.2
```
ステージング環境で 0.25.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

patch github.com
patch github.com
patch github.com