CVE-2024-9684
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 · uneditedFreyrSCADA/IEC-60870-5-104 server v21.06.008 allows remote attackers to cause a denial of service by sending specific message sequences.
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 confidenceFreyrSCADA IEC-60870-5-104 server version 21.06.008 contains a denial-of-service vulnerability where remote attackers can cause the server to become unavailable by sending specific message sequences. The IEC-60870-5-104 protocol is commonly used in SCADA/ICS environments for power system automation and process control. The vulnerability allows unauthenticated remote attackers to crash the server without requiring any authentication or special privileges.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if FreyrSCADA IEC-60870-5-104 server is runningCheck running processes or services on the system for FreyrSCADA or iec104-related service names. On Windows, check Services control panel; on Linux, use 'ps aux' or 'systemctl list-units' to find the service.Affected if The FreyrSCADA IEC-60870-5-104 server service or process is present and running on the system
-
Determine the installed version of the IEC-60870-5-104 serverCheck the application's version information. Look in the installation directory for version files, check the service properties, or query the application directly if it exposes version via command line (e.g., 'iec104server -v' or similar). Compare the version to 21.06.008.Affected if The installed version is 21.06.008 or any earlier version of FreyrSCADA IEC-60870-5-104 server
-
Verify if TCP port 2404 is listeningUse netstat, ss, or PowerShell 'Get-NetTCPConnection' to check if port 2404 is in LISTEN state. Command examples: 'netstat -an | grep 2404' or 'ss -tlnp | grep 2404'.Affected if Port 2404 is open and listening, indicating the IEC-104 protocol service is exposed
-
Check network accessibility of port 2404From an external system or using network scanning tools, determine if port 2404 is reachable. Use 'nmap -p 2404 <target>' or telnet to test connectivity. Assess whether the port is exposed to untrusted networks.Affected if Port 2404 is accessible from network segments that contain untrusted or unauthorized systems
If the FreyrSCADA IEC-60870-5-104 server version 21.06.008 or earlier is running with TCP port 2404 accessible from the network, the environment is vulnerable to this denial-of-service flaw.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied patch or update to a patched version of FreyrSCADA/IEC-60870-5-104 server. Additionally, implement network segmentation and firewall rules to restrict access to the 104 protocol port (typically TCP 2404) to only authorized IP addresses and monitoring systems.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9684 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9684 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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