Elvish is a programming language and interactive shell, combined into one package. In versions prior to 0.14.0 Elvishs web UI backend (started by elvish -web) hosts an endpoint that allows executing the code sent from the web UI. The backend does not check the origin of requests correctly. As a result, if the user has the web UI backend open and visits a compromised or malicious website, the website can send arbitrary code to the endpoint in localhost. All Elvish releases from 0.14.0 onward no longer include the the web UI, although it is still possible for the user to build a version from source that includes the web UI. The issue can be patched for previous versions by removing the web UI (found in web, pkg/web or pkg/prog/web, depending on the exact version).
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Elvish | Elv | * | 0.14.0 (excluding) |
| Elvish | Ubuntu | bionic | * |
| Elvish | Ubuntu | hirsute | * |
| Elvish | Ubuntu | impish | * |
| Elvish | Ubuntu | kinetic | * |
| Elvish | Ubuntu | lunar | * |
| Elvish | Ubuntu | mantic | * |
| Elvish | Ubuntu | trusty | * |
| Elvish | Ubuntu | xenial | * |
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.