Template injection in the publishing component of awslabs Virtual Engineering Workbench
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| AWS | virtual-engineering-workbench | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aws | Virtual-engineering-workbench |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.554% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Improper neutralization of special elements used in a template engine in the publishing component of Amazon Virtual Engineering Workbench (VEW) could allow a remote authenticated third party to run arbitrary code with the permissions of the publishing Lambda's IAM role. This could allow access to data and resources across all tenant projects. The code is reachable through a crafted CloudFormation template body containing template engine directives submitted through the product versioning API. To remediate this issue, users should redeploy from the latest version of awslabs/virtual-engineering-workbench. | |
| Title | Template injection in the publishing component of awslabs Virtual Engineering Workbench | |
| First Time appeared |
Aws
Aws virtual-engineering-workbench |
|
| Weaknesses | CWE-1336 | |
| CPEs | cpe:2.3:a:aws:virtual-engineering-workbench:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aws
Aws virtual-engineering-workbench |
|
| References |
| |
| Metrics |
cvssV3_1
|