CORE-01: Core dump exposure¶
| Property | Value |
|---|---|
| Severity | high |
| Platform | AWS Nitro Enclaves |
| Lifecycle stage | runtime |
| Mode | Active: runs fixed read-only commands on the host. Skipped with --read-only. |
What it checks¶
It passes when:
- Core dumps are disabled.
Example failures:
- Core dumps are enabled: …. A crash could write enclave secrets to host disk in plaintext.
- Core dumps are enabled: kernel.core_pattern=|/usr/lib/systemd/systemd-coredump | ulimit core=unlimited. A crash could write enclave secrets to host disk in plaintext.
How to fix¶
- Disable core dumps: echo 'kernel.core_pattern=|/bin/false' >> /etc/sysctl.conf && sysctl -p && echo '* hard core 0' >> /etc/security/limits.conf
- Disable core dumps: set kernel.core_pattern=|/bin/false and ulimit hard core 0.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No instance ID specified; skipping check.
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--instance-id |
EC2 instance ID running the Nitro Enclave. |
--region |
AWS region. |
Permissions¶
The cloud API calls this check makes, read from the scanner's source:
| Cloud | API call | Permission | Access |
|---|---|---|---|
| AWS | ssm.get_command_invocation |
ssm:GetCommandInvocation |
read |
| AWS | ssm.send_command |
ssm:SendCommand |
run command |
Every AWS scan also calls sts:GetCallerIdentity. See Required permissions for a complete policy.
Evidence recorded¶
Keys in the finding's evidence: core_pattern, ulimit_core
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).