dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-44043

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Keyoti SearchUnit prior to 9.0.0. is vulnerable to Server-Side Request Forgery (SSRF) in /Keyoti_SearchEngine_Web_Common/SearchService.svc/GetResults and /Keyoti_SearchEngine_Web_Common/SearchService.svc/GetLocationAndContentCategories. An attacker can specify their own SMB server as the indexDirectory value when making POST requests to the affected components. In doing so an attacker can get the SearchUnit server to read and write configuration and log files from/to the attackers server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Keyoti SearchUnit before version 9.0.0 contains an SSRF vulnerability in the SearchService.svc endpoints (GetResults and GetLocationAndContentCategories). By supplying a malicious SMB server URL as the indexDirectory parameter in POST requests, attackers can force the SearchUnit server to read and write configuration and log files to/from the attacker-controlled server.

MitigationUpgrade to Keyoti SearchUnit version 9.0.0 or later, which contains the security fix for this SSRF vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Keyoti SearchUnit installation
    Search for SearchUnit DLLs, SearchService.svc files, or Keyoti assemblies in the application bin directory and web root. Check for 'Keyoti.SearchUnit' namespaces in deployed assemblies.
    Affected if Keyoti SearchUnit components are found in the environment
  2. Identify installed SearchUnit version
    Check the Keyoti SearchUnit DLL version properties (right-click DLL, view Details), or examine version info in the bin folder. Common files: Keyoti.SearchUnit.dll, Keyoti.SearchEngine.dll. Compare against version 9.0.0.
    Affected if Installed version is earlier than 9.0.0 or version cannot be determined
  3. Verify SearchService.svc endpoint exposure
    Check web.config or application routing configuration for mapped SearchService.svc endpoints. Look for GetResults and GetLocationAndContentCategories service methods.
    Affected if SearchService.svc with GetResults or GetLocationAndContentCategories endpoints is accessible via HTTP/HTTPS
  4. Review indexDirectory configuration
    Search configuration files (web.config, app.config, search settings XML/JSON) for indexDirectory parameter settings. Check if user-supplied or external input can set this value.
    Affected if indexDirectory parameter accepts external/untrusted input or is configurable via HTTP POST requests
  5. Inspect for anomalous outbound connections
    Review application logs, proxy logs, or network monitoring for outbound SMB connections to external/unexpected IP addresses or hostnames, particularly on ports 445 or 139.
    Affected if Outbound connections to attacker-controlled SMB servers are observed in logs or network traffic

The environment is affected if Keyoti SearchUnit is present with a version earlier than 9.0.0 AND the SearchService.svc endpoints are externally accessible, allowing the indexDirectory parameter to be controlled by attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Keyoti SearchUnit version 9.0.0 or later, which contains the security fix for this SSRF vulnerability.

Recommended fix High confidence

Keyoti SearchUnit 9.0.0 or later

  1. 1. Back up the current Keyoti SearchUnit installation, configuration files, and any custom settings
  2. 2. Download Keyoti SearchUnit version 9.0.0 or later from the official Keyoti vendor site
  3. 3. Review the official upgrade documentation provided by Keyoti for any specific migration requirements
  4. 4. Install version 9.0.0 or later following the vendor's standard upgrade procedure
  5. 5. Restore any custom configuration settings from the backup
  6. 6. Verify the upgrade was successful by confirming the SearchUnit application functions normally
  7. 7. Test that the previously vulnerable endpoints (/Keyoti_SearchEngine_Web_Common/SearchService.svc/GetResults and /Keyoti_SearchEngine_Web_Common/SearchService.svc/GetLocationAndContentCategories) no longer accept arbitrary SMB server specifications in the indexDirectory parameter

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-44043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-44043 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data