Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1110 CNY

100%

CVE-2018-1305 PoC — Apache Tomcat 访问控制错误漏洞

Source
Associated Vulnerability
Title:Apache Tomcat 访问控制错误漏洞 (CVE-2018-1305)
Description:Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them.
Description
Apache Tomcat 安全绕过漏洞 Poc
Readme
# Apache Tomcat 安全绕过漏洞
 
![exploit](https://github.com/iBearcat/CVE-2018-1305/blob/master/img/tomcat.jpg?raw=true)

近日,Apache发布安全公告称Apache Tomcat 7、8、9多个版本存在安全绕过漏洞。攻击者可以利用这个问题,绕过某些安全限制来执行未经授权的操作,这可能有助于进一步攻击。

Apache Tomcat servlet 注释定义的安全约束,只在servlet加载后才应用一次。由于以这种方式定义的安全约束,应用于URL模式及该点下任何URL,很可能取决于servlet加载的次序,这可能会将资源暴露给未经授权访问它们的用户。

## 漏洞编号

CVE-2018-1305

## 影响版本

Apache Tomcat < 9.0.5

Apache Tomcat < 8.5.28

Apache Tomcat < 8.0.50

Apache Tomcat < 7.0.85

## 威胁等级

中危

## 漏洞复现

Java EE 提供了类似 ACL 权限检查的ServletSecurity注解,可以用于修饰Servlet对其进行保护,如果有两个servlet,Servlet1,访问路径为“/servlet1/*”并且添加了ServletSecurity注解,Servlet2,访问路径为“/servlet1/servlet2/*”但没有ServletSecurity注解,首次访问servlet1/servlet2,servlet1的ServletSecurity注解并不会生效,无法保护“/servlet1/servlet2”路径,因此可能会导致未授权访问。

如果在访问“/servlet1/servlet2”之前先访问过“/servlet1”,Tomcat会加载ACL并启动对“/servlet1/servlet2”的保护,则漏洞不会触发。

![exploit](https://github.com/iBearcat/CVE-2018-1305/blob/master/img/1.jpg?raw=true)

在Servlet1前加上ServletSecurity注解,Servlet2无此注解。

![exploit](https://github.com/iBearcat/CVE-2018-1305/blob/master/img/2.jpg?raw=true)

将web.xml文件中servlet相对应的url-pattern修改为如下图所示后。

![exploit](https://github.com/iBearcat/CVE-2018-1305/blob/master/img/3.jpg?raw=true)

运行该项目。首次访问servlet2的URL,发现可以未授权访问,针对servlet1的ACL并未生效。

http://localhost:8080/CVE-2018-1305/servlet1/servlet2/

![exploit](https://github.com/iBearcat/CVE-2018-1305/blob/master/img/4.jpg?raw=true)

第二次访问servlet1的URL,访问被禁止,此时ACL生效。

http://localhost:8080/CVE-2018-1305/servlet1/

![exploit](https://github.com/iBearcat/CVE-2018-1305/blob/master/img/5.jpg?raw=true)

再次访问servlet2的URL,发现访问被禁止,如果ACL对servlet2生效,必须建立在servlet1被访问过的前提下。

http://localhost:8080/CVE-2018-1305/servlet1/servlet2/

![exploit](https://github.com/iBearcat/CVE-2018-1305/blob/master/img/6.jpg?raw=true)

## 漏洞演示

![exploit](https://github.com/iBearcat/CVE-2018-1305/blob/master/img/Demonstration.gif?raw=true)

因此漏洞的复现仅限于Tomcat启动后,在访问“/servlet1/*”之前先访问了“/servlet1/servlet2/*”页面,若之前存在任何人访问“/servlet1/*”页面,则漏洞不会触发。漏洞危害较高,但是利用条件困难,因此影响范围并不大。

## 相关链接
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1305

http://blog.nsfocus.net/cve-2018-130-handling/

https://www.anquanke.com/post/id/99213
File Snapshot

[4.0K] /data/pocs/dbb5965148a7d43d02ee550b4e5789b2b6e66fc5 ├── [4.0K] CVE-2018-1305 │   ├── [4.0K] build │   │   └── [4.0K] classes │   │   └── [4.0K] servlet │   │   ├── [1.2K] Servlet1.class │   │   └── [ 825] Servlet2.class │   ├── [4.0K] src │   │   └── [4.0K] servlet │   │   ├── [ 605] Servlet1.java │   │   └── [ 456] Servlet2.java │   └── [4.0K] WebContent │   ├── [4.0K] images │   │   └── [217K] logo.jpg │   ├── [ 577] index.jsp │   ├── [4.0K] META-INF │   │   └── [ 39] MANIFEST.MF │   └── [4.0K] WEB-INF │   ├── [4.0K] lib │   │   └── [ 18K] annotations-api.jar │   └── [ 796] web.xml ├── [233K] CVE-2018-1305.war ├── [4.0K] img │   ├── [ 30K] 1.jpg │   ├── [ 24K] 2.jpg │   ├── [ 30K] 3.jpg │   ├── [6.4K] 4.jpg │   ├── [ 13K] 5.jpg │   ├── [ 14K] 6.jpg │   ├── [365K] Demonstration.gif │   └── [217K] tomcat.jpg └── [3.1K] README.md 12 directories, 19 files
Shenlong Bot has cached this for you
Remarks
    1. It is advised to access via the original source first.
    2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.
    3. Mirroring, verifying, and maintaining this POC archive takes ongoing effort, so local snapshots are a paid feature. Your subscription keeps the archive online — thank you for the support. View subscription plans →