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

CVE-2024-45317

HIGH · 7.5 CVSS v3.1 Published 2024-10-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A Server-Side Request Forgery (SSRF) vulnerability in SMA1000 appliance firmware versions 12.4.3-02676 and earlier allows a remote, unauthenticated attacker to cause the SMA1000 server-side application to make requests to an unintended IP address.

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

SSRF vulnerability in SMA1000 appliance firmware versions 12.4.3-02676 and earlier allows a remote, unauthenticated attacker to induce the server-side application to perform HTTP requests to attacker-controlled or unintended IP addresses.

MitigationUpgrade SMA1000 firmware to a version newer than 12.4.3-02676; apply network segmentation or outbound firewall rules to restrict the appliance's ability to connect to arbitrary IPs as a compensating control until patching is complete.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 SMA1000 appliance model
    Access the appliance's web management console or use CLI commands such as 'show system info' or 'get system status' to identify the device model. Look for 'SMA1000' or 'SMA 100' in the model identifier.
    Affected if The device is not an SMA1000 appliance (different models are not affected by this specific CVE).
  2. Check installed firmware version
    In the web interface, navigate to System > Firmware or use the CLI command 'firmware version'. Compare the displayed version number to 12.4.3-02676. Versions at or below 12.4.3-02676 are affected.
    Affected if The firmware version is 12.4.3-02676 or any earlier version (for example, 12.4.2-XXXX or 12.3.x).
  3. Verify web management interface accessibility
    Determine if the SMA1000 web management interface (typically ports 443 or 8443) is exposed to untrusted networks or the internet. Check firewall rules or network access lists.
    Affected if The web interface is directly accessible from untrusted networks (such as the internet) without VPN or IP allowlist restrictions, allowing unauthenticated attackers to reach the vulnerable endpoint.
  4. Inspect outbound network connections
    Review firewall or network segmentation rules to determine if the SMA1000 appliance has unrestricted ability to initiate outbound HTTP connections to arbitrary IP addresses.
    Affected if The appliance has unrestricted outbound internet access and can connect to arbitrary external IP addresses, enabling the SSRF to reach attacker-controlled endpoints.

A user is affected if they are running SMA1000 firmware version 12.4.3-02676 or earlier and the web interface is accessible to unauthenticated 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 SMA1000 firmware to a version newer than 12.4.3-02676; apply network segmentation or outbound firewall rules to restrict the appliance's ability to connect to arbitrary IPs as a compensating control until patching is complete.

Recommended fix Moderate confidence

Any SMA1000 firmware release later than 12.4.3‑02676 (e.g., 12.4.3‑03000 or the latest stable release)

  1. Log in to the SMA1000 admin web UI or console and note the current firmware version (e.g., from the Dashboard or via CLI command "show version").
  2. Navigate to the SonicWall support portal (https://support.sonicwall.com) and locate the SMA1000 firmware downloads section.
  3. Download the latest SMA1000 firmware version that is newer than 12.4.3-02676 (or the specific version indicated in the SonicWall advisory for CVE‑2024‑45317).
  4. In the SMA1000 web UI, go to System > Firmware Upgrade, select the downloaded firmware file, and upload it.
  5. After the upload completes, apply the upgrade and allow the appliance to reboot.
  6. Once the device restarts, log in again and verify that the displayed firmware version is greater than 12.4.3‑02676, confirming the fix.
Caveat Firmware upgrade may cause a brief service disruption; test in a non‑production environment before deploying to production.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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