CVE-2024-0860
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 · uneditedThe affected product is vulnerable to a cleartext transmission of sensitive information vulnerability, which may allow an attacker to capture packets to craft their own requests.
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 · low confidenceThe vulnerability involves cleartext transmission of sensitive information over the network, allowing an attacker using packet capture to intercept and view sensitive data in transit. This enables the attacker to capture packets and potentially craft malicious requests based on the intercepted information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.60= 3.60CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Softing product and versionLocate the Softing Edgeaggregator or Edgeconnector installation directory and check the version information file, or run the product's version command if available (e.g., 'edgeaggregator --version' or check in the product's About/Info panel)Affected if The installed version is exactly 3.60 for either Softing Edgeaggregator or Softing Edgeconnector
-
Review network communication settingsAccess the product configuration interface or config files and examine the network communication settings for enabled protocolsAffected if Protocols such as HTTP (non-TLS), plain OPC-UA without security, or other unencrypted communication methods are enabled
-
Inspect active network listeners and portsUse netstat or similar network tools to list active listening ports and connections established by the Softing product processAffected if The product is listening on or communicating over non-encrypted ports (e.g., HTTP port 80, OPC-UA binary without security) rather than secure ports (HTTPS, OPC-UA with TLS)
-
Capture and analyze network trafficUse a packet capture tool (e.g., Wireshark, tcpdump) to capture traffic to/from the Softing product and inspect payload contentsAffected if Sensitive data such as credentials, configuration details, or operational data is visible in cleartext within captured packets
Your environment is affected if Softing Edgeaggregator or Edgeconnector version 3.60 is running and transmitting sensitive data over unencrypted network connections.
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 dataImplement TLS/SSL encryption or other cryptographic protocols for all sensitive data transmissions to prevent packet capture and interception of cleartext traffic.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0860 — 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-0860 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