intel / intel/confidential-computing.sgx

Check whether the /run/aesmd/aesm.socket exposure permission is too large. Is it safe?

Open
#836 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
1.5k
Forks
565
PR merge metrics
No merged PRs in 30d

Description

```
ll /run/aesmd/aesm.socket
srwxrwxrwx. 1 aesmd aesmd 0 Apr 21 15:50 /run/aesmd/aesm.socket
```

[Types of attacks malware can carry out by exploiting Unix domain sockets](https://jiayunhan.github.io/material/misuse_ccs16.pdf)
| Role | Prerequisite(s) | Attacks |
| ---- | ---- | ---- |
| Malicous Server | 1) Start running ahead of the real server 2) Client has no/weak authentication of server | Data Leakage/Injection, DoS |
| Malicous Client | Server has no/weak authentication of client | Privilege Escalation, Data Leakage/Injection, DoS |

Other users can read and write. Is it too easy to launch attacks? Is this safe?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.