DNS rebinding vulnerability in rojo serve HTTP API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| rojo-rbx | rojo | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Rojo-rbx | Rojo |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.260% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rojo-rbx
Rojo-rbx rojo |
|
| Vendors & Products |
Rojo-rbx
Rojo-rbx rojo |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Rojo's "rojo serve" HTTP API (default port 34872) has no Host/Origin header validation, making it vulnerable to DNS rebinding. A malicious webpage can read all project source, write malicious code to files on disk, and launch local programs via opener::open() with no user interaction beyond visiting the page. | |
| Title | DNS rebinding vulnerability in rojo serve HTTP API | |
| Weaknesses | CWE-350 | |
| References |
| |
| Metrics |
cvssV3_1
|