FKIE_CVE-2025-0184

Vulnerability from fkie_nvd - Published: 2025-03-20 10:15 - Updated: 2025-07-15 15:41
Severity ?
6.5 (Medium) - CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Summary
A Server-Side Request Forgery (SSRF) vulnerability was identified in langgenius/dify version 0.10.2. The vulnerability occurs in the 'Create Knowledge' section when uploading DOCX files. If an external relationship exists in the DOCX file, the reltype value is requested as a URL using the 'requests' module instead of the 'ssrf_proxy', leading to an SSRF vulnerability. This issue was fixed in version 0.11.0.
References
security@huntr.devhttps://github.com/langgenius/dify/commit/c135ec4b08d946a1a1d3a198a1d72c1ccf47250fPatch
security@huntr.devhttps://huntr.com/bounties/a7eac4ae-5d5e-4ac1-894b-7a8cce5cba9bExploit, Third Party Advisory
Impacted products
Vendor Product Version
langgenius dify *
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:langgenius:dify:*:*:*:*:*:node.js:*:*",
              "matchCriteriaId": "BD57180F-1305-43F5-BD43-A397F3D3DE21",
              "versionEndExcluding": "0.11.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "A Server-Side Request Forgery (SSRF) vulnerability was identified in langgenius/dify version 0.10.2. The vulnerability occurs in the \u0027Create Knowledge\u0027 section when uploading DOCX files. If an external relationship exists in the DOCX file, the reltype value is requested as a URL using the \u0027requests\u0027 module instead of the \u0027ssrf_proxy\u0027, leading to an SSRF vulnerability. This issue was fixed in version 0.11.0."
    },
    {
      "lang": "es",
      "value": "Se identific\u00f3 una vulnerabilidad de Server-Side Request Forgery (SSRF) en langgenius/dify versi\u00f3n 0.10.2. La vulnerabilidad se produce en la secci\u00f3n \"Crear conocimiento\" al subir archivos DOCX. Si existe una relaci\u00f3n externa en el archivo DOCX, el valor reltype se solicita como URL mediante el m\u00f3dulo \"requests\" en lugar de \"ssrf_proxy\", lo que genera una vulnerabilidad SSRF. Este problema se solucion\u00f3 en la versi\u00f3n 0.11.0."
    }
  ],
  "id": "CVE-2025-0184",
  "lastModified": "2025-07-15T15:41:34.817",
  "metrics": {
    "cvssMetricV30": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 6.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
          "version": "3.0"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 3.6,
        "source": "security@huntr.dev",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-03-20T10:15:51.173",
  "references": [
    {
      "source": "security@huntr.dev",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/langgenius/dify/commit/c135ec4b08d946a1a1d3a198a1d72c1ccf47250f"
    },
    {
      "source": "security@huntr.dev",
      "tags": [
        "Exploit",
        "Third Party Advisory"
      ],
      "url": "https://huntr.com/bounties/a7eac4ae-5d5e-4ac1-894b-7a8cce5cba9b"
    }
  ],
  "sourceIdentifier": "security@huntr.dev",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-918"
        }
      ],
      "source": "security@huntr.dev",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.