用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-ubuntu1804-v220-1-5-2命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-ubuntu1804-v220-1-5-2 |
| description | Ensure core dumps are restricted |
| category | cis-storage |
| version | 2.2.0 |
| author | cyberstrike-official |
| tags | ["cis","ubuntu","linux","ubuntu-18.04","core-dumps","process-hardening","security"] |
| cis_id | 1.5.2 |
| cis_benchmark | CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0 |
| tech_stack | ["ubuntu","linux"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
A core dump is the memory of an executable program. It is generally used to determine why a program aborted. It can also be used to glean confidential information from a core file. The system provides the ability to set a soft limit for core dumps, but this can be overridden by the user.
Setting a hard limit on core dumps prevents users from overriding the soft variable. If core dumps are required, consider setting limits for user groups (see limits.conf(5)). In addition, setting the fs.suid_dumpable variable to 0 will prevent setuid programs from dumping core.
Run the following command and verify output matches:
grep -Es '^(\*|\s).*hard.*core.*(\s+#.*)?$' /etc/security/limits.conf /etc/security/limits.d/*
Run the following script to verify fs.suid_dumpable = 0:
#!/usr/bin/env bash
{
l_output="" l_output2=""
a_parlist=("fs.suid_dumpable=0")
l_ufwscf="$([ -f /etc/default/ufw ] && awk -F= '/^\s*IPT_SYSCTL=/ {print $2}' /etc/default/ufw)"
a_searchpath=("/run/sysctl.d/" "/etc/sysctl.d/" "/usr/local/lib/sysctl.d/" "/usr/lib/sysctl.d/" "/lib/sysctl.d/")
unset A_files
declare -A A_files
A_files+=(["sysctl.conf"]="/etc/sysctl.conf")
for l_searchpath in "${a_searchpath[@]}"; do
if [ -d "$l_searchpath" ]; then
while IFS= read -r -d $ l_filename;
[ -f ];
l_basename=
[ -z ];
A_files+=([]=)
< <(find - f -name -print0)
a_sorted=()
IFS= -rd l_key;
a_sorted+=( )
< <( | -rz)
()
{
l_var= l_var2=
l_krp=
[ = ];
l_output=
l_output2=
}
IFS= -r l_kpname l_kpvalue;
l_kpname=; l_kpvalue=
kernel_parameter_chk
< <( )
A_files; a_sorted
[ -z ];
-e
-e
[ -n ] && -e
}
Run the following command to check if systemd-coredump is installed:
systemctl is-enabled coredump.service
If enabled, masked, or disabled is returned systemd-coredump is installed.
* hard core 0
Add the following line to /etc/security/limits.conf or a /etc/security/limits.d/* file:
* hard core 0
Set the following parameter in /etc/sysctl.conf or a file in /etc/sysctl.d/ ending in .conf:
fs.suid_dumpable = 0Example:
printf '%s\n' "fs.suid_dumpable = 0" >> /etc/sysctl.d/60-fs_sysctl.conf
Run the following command to set the active kernel parameter:
sysctl -w fs.suid_dumpable=0
Note: If these settings appear in a conically later file, or later in the same file, these settings will be overwritten.
IF systemd-coredump is installed: edit /etc/systemd/coredump.conf and add/modify the following lines:
Storage=none
ProcessSizeMax=0
Run the command:
systemctl daemon-reload
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|
| Techniques / Sub-techniques | Tactics | Mitigations |
|---|---|---|
| T1005, T1005.000 | TA0007 | M1057 |