You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rule descriptions are not up-to-date with the latest STIG.
For example, after the update of the RHEL 9 STIG, the policy/stig/shared.yml description of the sysctl_kernel_yama_ptrace_scope rule was updated:
But the vuln_discussion section is duplicated. The first one is the previous one and the new one appears at the end of the file.
vuldiscussion: |-
Unrestricted usage of ptrace allows compromised binaries to run ptrace on another processes of the user. Like this, the attacker can steal
sensitive information from the target processes (e.g. SSH sessions, web browser, etc) without any additional assistance from the user (i.e. without resorting to phishing).
[...]
vuln_discussion: |-
Unrestricted usage of ptrace allows compromised binaries to run ptrace on other processes of the user. Like this, the attacker can steal sensitive information from the target processes (e.g., SSH sessions, web browser, etc.) without any additional assistance from the user (i.e., without resorting to phishing).
rationale: |
Unrestricted usage of ptrace allows compromised binaries to run ptrace
on another processes of the user. Like this, the attacker can steal
sensitive information from the target processes (e.g. SSH sessions, web browser, ...)
without any additional assistance from the user (i.e. without resorting to phishing).
Description of problem:
The rule descriptions are not up-to-date with the latest STIG.
For example, after the update of the RHEL 9 STIG, the policy/stig/shared.yml description of the
sysctl_kernel_yama_ptrace_scope
rule was updated:But the
vuln_discussion
section is duplicated. The first one is the previous one and the new one appears at the end of the file.And the rule.yml description was not updated:
SCAP Security Guide Version:
master
branch as of 2024-06-24 (644de12).The text was updated successfully, but these errors were encountered: