mirror of
https://github.com/e-m-b-a/emba.git
synced 2026-10-12 02:13:21 +00:00
Merge pull request #2119 from e-m-b-a/m-1-k-3-patch-12
Update SECURITY.md with changes and new contacts
This commit is contained in:
+4
-1
@@ -4,13 +4,14 @@ _EMBA_ is a platform for optimizing our research and testing tasks in the field
|
||||
|
||||
# WARNING
|
||||
|
||||
_EMBA_ is using multiple protection layers like chroot, docker, read-only filesystem, non executable mounts and disabled networking functionality.
|
||||
_EMBA_ is using multiple protection layers like chroot, docker, non executable mounts and disabled networking functionality.
|
||||
Nevertheless, _EMBA_ should only be used on test systems! It should not be installed/deployed on production systems.
|
||||
|
||||
There are multiple reasons for that:
|
||||
* The _EMBA_ docker container is running in privileged mode which will result in full system compromise if you are testing malicious firmware.
|
||||
* _EMBA_ automatically executes untrusted code from the firmware which could lead to breakouts that are able to compromise the host system.
|
||||
* _EMBA_ automatically builds and boots a firmware image based on the untrusted firmware under test.
|
||||
* _EMBA_ is heavily based on a lot of different components that are sometimes outdated and not well maintained anymore.
|
||||
|
||||
## Reporting a Vulnerability
|
||||
|
||||
@@ -19,3 +20,5 @@ If there is a security problem within _EMBA_ please open an issue or contact us
|
||||
* [Start a Discussion](https://github.com/e-m-b-a/emba/discussions)
|
||||
* [PM us via Twitter](https://twitter.com/securefirmware)
|
||||
* [PM us via Mastodon](https://infosec.exchange/@securefirmware)
|
||||
* [PM us via BlueSky](https://bsky.app/profile/securefirmware.bsky.social)
|
||||
* [Contact me directly on LinkedIn](https://www.linkedin.com/in/michael-messner-4421243a/)
|
||||
|
||||
Reference in New Issue
Block a user