nuclei-templates/cves/2018/CVE-2018-11759.yaml

id: CVE-2018-11759

info:
  name: Apache Tomcat JK Status Manager Access
  author: harshbothra_
  severity: medium
  reference: https://github.com/immunIT/CVE-2018-11759
  tags: cve,cve2018,apache

requests:
  - method: GET
    path:
      - '{{BaseURL}}/jkstatus'
      - '{{BaseURL}}/jkstatus;'

    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "JK Status Manager"
misc changes 2021-01-02 05:00:39 +00:00			`id: CVE-2018-11759`
Create CVE-2018-11759.yaml Apache Tomcat JK Status Manager Access 2020-07-06 16:28:42 +00:00
			`info:`
			`name: Apache Tomcat JK Status Manager Access`
Updated author names 2021-06-09 12:20:56 +00:00			`author: harshbothra_`
adding both path for possilbe use cases 2020-08-06 08:12:12 +00:00			`severity: medium`
Added tags to cves :sunglasses: (#813) * Added tags to cves :sunglasses: 2021-02-05 19:44:41 +00:00			`reference: https://github.com/immunIT/CVE-2018-11759`
			`tags: cve,cve2018,apache`
Create CVE-2018-11759.yaml Apache Tomcat JK Status Manager Access 2020-07-06 16:28:42 +00:00
			`requests:`
			`- method: GET`
			`path:`
adding both path for possilbe use cases 2020-08-06 08:12:12 +00:00			`- '{{BaseURL}}/jkstatus'`
Add semicolon to path The vulnerability is that access restriction can be circumvented by adding a semicolon to the path (as pointed out in https://github.com/immunIT/CVE-2018-11759). Without semicolon, jkstatus would be public anyway and would not be related to the CVE. 2020-08-06 08:06:13 +00:00			`- '{{BaseURL}}/jkstatus;'`
Create CVE-2018-11759.yaml Apache Tomcat JK Status Manager Access 2020-07-06 16:28:42 +00:00
Update CVE-2018-11759.yaml 2020-07-06 17:13:45 +00:00			`matchers-condition: and`
Create CVE-2018-11759.yaml Apache Tomcat JK Status Manager Access 2020-07-06 16:28:42 +00:00			`matchers:`
			`- type: status`
			`status:`
			`- 200`
			`- type: word`
			`words:`
			`- "JK Status Manager"`