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

CVE-2024-13957

HIGH · 7.6 CVSS v3.1 Published 2025-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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
SSRF Server Side Request Forgery vulnerabilities exist in ASPECT if administrator credentials become compromisedThis issue affects ASPECT-Enterprise: through 3.*; NEXUS Series: through 3.*; MATRIX Series: through 3.*.

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

SSRF (Server Side Request Forgery) vulnerabilities exist in ASPECT product lines (ASPECT-Enterprise, NEXUS Series, and MATRIX Series all through version 3.*). The vulnerability allows server-side requests to be made, specifically when administrator credentials become compromised, potentially enabling attackers to access internal resources or services.

MitigationRestrict and validate all server-side request capabilities, implement strict allowlist-based URL validation, enforce network segmentation to prevent internal resource access, and rotate compromised administrator credentials immediately.

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
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/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. Identify the installed ASPECT product
    Locate the product name in the system documentation, web interface header, or installation directory. The affected products are ASPECT-Enterprise, NEXUS Series, and MATRIX Series.
    Affected if The product is one of these three lines and runs version 3.* through 3.x.x
  2. Determine the installed software version
    Access the administrator web interface or check the product's about/version panel in the software. Compare the version number to the affected range (3.*).
    Affected if The version number begins with 3 (such as 3.0, 3.1, 3.5, 3.10) indicating it is within the 3.x release line
  3. Verify administrator credentials are not compromised
    Review active administrator accounts in the user management section. Check for any unauthorized accounts or recent credential changes. Verify that default administrator passwords have been changed.
    Affected if Default credentials are still in use, or unknown administrator accounts exist, or credentials were changed without admin action
  4. Confirm exposure of administrator web interface
    Check network configuration to determine if the ASPECT administrator panel is accessible from untrusted networks. Review firewall rules and access control lists.
    Affected if The admin interface is directly exposed to the internet or untrusted networks without VPN or IP restriction
  5. Inspect server-side request configuration
    Examine the product configuration settings for any URL request, webhook, or external integration features. Look for options that allow the server to make outbound HTTP requests.
    Affected if Server-side request features are enabled and accessible to compromised administrator accounts
  6. Review access and network logs for internal resource requests
    Analyze server logs for requests to internal IP addresses (such as 10.x.x.x, 192.168.x.x, 127.0.0.1) or internal hostnames that the ASPECT server should not normally access.

A user is affected if they run ASPECT-Enterprise, NEXUS Series, or MATRIX Series version 3.x and the administrator interface or server-side request features are accessible, particularly if credentials may be compromised.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict and validate all server-side request capabilities, implement strict allowlist-based URL validation, enforce network segmentation to prevent internal resource access, and rotate compromised administrator credentials immediately.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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