dbcve.org
EdgeaggregatorWeb browser · Softing

CVE-2023-39482

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.30 / 3.70 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Softing Secure Integration Server Hardcoded Cryptographic Key Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Softing Secure Integration Server. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within libopcuaclient.so. The issue results from hardcoding crytographic keys within the product. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-20610.

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

Hardcoded cryptographic keys embedded in libopcuaclient.so of Softing Secure Integration Server allow authenticated attackers (or those bypassing authentication) to disclose stored credentials. The flaw enables further compromise by exposing sensitive authentication material stored by the product.

MitigationReplace hardcoded cryptographic keys with properly managed keys, rotate any exposed credentials, and apply vendor patches if available. Review access controls and monitor for credential reuse across systems.

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
EdgeaggregatorWeb browser
Affected:< 3.70
EdgeconnectorWeb browser
Affected:< 3.70
Secure Integration ServerApplication
Affected:< 1.30

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify installed product version
    Run the product's version command or check its about/info panel. For Softing Edgeaggregator, Edgeconnector, or Secure Integration Server, use: docker ps (if containerized) or check the installed package version via the system package manager. Look for version information in /opt/softing/ or the product's installation directory.
    Affected if The installed version is less than 3.70 for Edgeaggregator/Edgeconnector, or less than 1.30 for Secure Integration Server.
  2. Locate libopcuaclient.so library file
    Search for the vulnerable library: find / -name 'libopcuaclient.so' 2>/dev/null or check in common installation paths like /opt/softing/, /usr/lib/, or the product's bin/lib directory. Use 'ls -la' on the found file to confirm its presence and modification date.
    Affected if The library file exists on the system, indicating the vulnerable component is present.
  3. Verify credential storage is in use
    Check the product's configuration files or database for stored credentials. Look for credential-related directories (often named 'credentials', 'certs', 'keys', 'security') or configuration files (XML, JSON, YAML) that may contain encrypted or stored authentication material. Inspect the data directory where the product stores user credentials or integration credentials.
    Affected if The product is configured to store credentials (user accounts, integration credentials, or authentication tokens) that would be protected by the hardcoded keys.
  4. Review authentication configuration
    Examine the product's authentication settings in its configuration files or admin interface. Check whether authentication is enabled and whether the product stores credentials locally. Look for settings related to user authentication, API keys, or integration credentials stored on the system.
    Affected if Local authentication storage is enabled, meaning the hardcoded keys could be used to decrypt stored credentials.

A system is affected if it runs any of the three Softing products with a version below the threshold AND has the libopcuaclient.so library present with stored credentials that rely on the hardcoded cryptographic keys.

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
Upgrade available Upgrade to 1.30 / 3.70 or later
Fixed in 1.303.70
Interim mitigation

Replace hardcoded cryptographic keys with properly managed keys, rotate any exposed credentials, and apply vendor patches if available. Review access controls and monitor for credential reuse across systems.

Fix this in Edgeaggregator Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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