browser-use web-ui 2.0.0 through 3.0.0 Cleartext API Key Storage
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| browser-use | web-ui | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Browser-use | Browser Use |
|
||||||||
| Browser-use | Web-ui |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.072% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Browser-use web-ui
|
|
| Vendors & Products |
Browser-use web-ui
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | browser-use web-ui versions 2.0.0 through 3.0.0 write configured LLM API keys to disk in cleartext without encryption or access restrictions. Attackers with read access to the temporary settings directory can recover provider API keys from predictably-named JSON files. | |
| Title | browser-use web-ui 2.0.0 through 3.0.0 Cleartext API Key Storage | |
| First Time appeared |
Browser-use
Browser-use browser Use |
|
| Weaknesses | CWE-312 | |
| CPEs | cpe:2.3:a:browser-use:browser_use:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Browser-use
Browser-use browser Use |
|
| References |
| |
| Metrics |
cvssV3_1
|