Imported from urtir/SiagaSiber (
.siaga/skill/CIS_benchmarks/Server_Software/Apache_Tomcat/CIS_Apache_Tomcat_8_Benchmark_v1.1.0/cis-tomcat8-v110-10.12/SKILL.md). Install upstream withnpx skills add urtir/SiagaSiber --skill cis-tomcat8-v110-10.12. Copyright stays with the author.
10.12 Do not allow symbolic linking (Automated)
Description
Symbolic links permit one application to include the libraries from another. This allows for re-use of code but also allows for potential security issues when applications include libraries from other applications to which they should not have access.
Rationale
Allowing symbolic links makes Tomcat susceptible to directory traversal vulnerability. Also, there is a potential that an application could link to another application to which it should not be linking. On case-insensitive operating systems there is also the threat of source code disclosure.
Audit Procedure
Ensure the allowLinking attribute in all context.xml does not exist or is set to false.
# find . -name context.xml | xargs grep "allowLinking"
Remediation
In all context.xml, set the allowLinking attribute to false:
<Context>
...
<Resources ... allowLinking="false" />
...
</Context>Default Value
By default allowLinking has a value of false.
References
- https://tomcat.apache.org/tomcat-9.0-doc/config/resources.html
- https://tomcat.apache.org/tomcat-9.0-doc/config/context.html
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 2.7 Allowlist Authorized ScriptsUse technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently. | ● | ||
| v7 | 5.1 Establish Secure ConfigurationsMaintain documented, standard security configuration standards for all authorized operating systems and software. | ● | ● | ● |
Profile
Level 1
