KitchenOwl through 0.7.10 SSRF via Recipe Import scrapeKitchenOwl Fetch
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| TomBursch | kitchenowl | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tombursch | Kitchenowl |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.269% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tombursch
Tombursch kitchenowl |
|
| Vendors & Products |
Tombursch
Tombursch kitchenowl |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | KitchenOwl through 0.7.10 contains a server-side request forgery vulnerability in recipe import that allows authenticated household members to bypass IP filtering via a second unfiltered fetch. Attackers can host a page titled KitchenOwl at a URL matching /recipe/<id>. The follow-up requests.get() call can then be redirected or DNS-rebound to loopback, private-network, or cloud-metadata addresses, exposing internal services. | |
| Title | KitchenOwl through 0.7.10 SSRF via Recipe Import scrapeKitchenOwl Fetch | |
| Weaknesses | CWE-918 | |
| References |
|
|
| Metrics |
cvssV3_1
|