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

CVE-2024-27775

HIGH · 7.2 CVSS v3.1 Published 2024-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
SysAid before version 23.2.14 b18 - CWE-918: Server-Side Request Forgery (SSRF) may allow exposing the local OS user's NTLMv2 hash

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 · moderate confidence

Server-Side Request Forgery (SSRF) in SysAid before version 23.2.14 b18 allows attackers to induce the server to make arbitrary HTTP requests to internal or external resources. This can be leveraged to intercept NTLM authentication challenges and capture the local OS user's NTLMv2 hash, enabling relay attacks or offline cracking.

MitigationUpgrade SysAid to version 23.2.14 b18 or later to apply the vendor patch. Additionally, restrict outbound network access from the application server and consider disabling NTLM authentication where possible to reduce the impact of NTLM hash exposure.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify SysAid installation
    Locate the SysAid installation directory or running service. Common paths include C:\Program Files\SysAid or /opt/sysaid on Linux. Check running processes for SysAid-related Java or Tomcat services.
    Affected if SysAid software is found on the system
  2. Determine installed SysAid version
    Access the SysAid web interface and navigate to the About/Help section, or check version files in the installation directory (typically named version.txt, build.info, or displayed in the login page footer).
    Affected if Version is below 23.2.14 b18 (for example, 23.2.14 b17 or earlier)
  3. Check for exposed API endpoints
    Inspect the SysAid web application's exposed URLs, particularly any endpoints that accept external URLs or perform HTTP requests. Look for features like integrations, external links, or monitoring endpoints.
    Affected if URL-handling endpoints are accessible without authentication or with low-privilege access
  4. Verify NTLM authentication configuration
    Review SysAid authentication settings in the admin console or configuration files to confirm whether NTLM authentication is enabled for user logins.
    Affected if NTLM authentication is enabled, allowing potential hash interception
  5. Assess network accessibility
    Determine if the SysAid server is reachable from untrusted networks by reviewing firewall rules, reverse proxy configurations, or network segmentation settings.
    Affected if The SysAid web interface is accessible from networks outside the trusted internal zone

Environment is affected if SysAid version is below 23.2.14 b18 and the server is network-accessible with NTLM authentication enabled.

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 SysAid to version 23.2.14 b18 or later to apply the vendor patch. Additionally, restrict outbound network access from the application server and consider disabling NTLM authentication where possible to reduce the impact of NTLM hash exposure.

Recommended fix Moderate confidence

SysAid version 23.2.14 b18 or later

  1. 1. Identify current SysAid installation version via admin console or system information
  2. 2. Obtain SysAid version 23.2.14 b18 or later from official SysAid vendor channels
  3. 3. Create a complete backup of the current SysAid installation including database and configuration files
  4. 4. Stop the SysAid service before applying the upgrade
  5. 5. Apply the upgrade following SysAid's standard upgrade procedure for your deployment type (on-premise or managed)
  6. 6. Start the SysAid service and verify successful startup
  7. 7. Log in to the admin console and confirm the version has been updated to 23.2.14 b18 or later
  8. 8. Test critical functionality to ensure the upgrade did not break existing workflows
Caveat Review SysAid release notes for version 23.2.14 for any configuration or feature changes that may affect your deployment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27775 — 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-2024-27775 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