CVE-2023-37426
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 · uneditedEdgeConnect SD-WAN Orchestrator instances prior to the versions resolved in this advisory were found to have shared static SSH host keys for all installations. This vulnerability could allow an attacker to spoof the SSH host signature and thereby masquerade as a legitimate Orchestrator host.
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 confidenceEdgeConnect SD-WAN Orchestrator instances used shared static SSH host keys across all installations. This means the same cryptographic host key was deployed to every customer's Orchestrator, allowing an attacker who knows this key to spoof the SSH server and perform man-in-the-middle attacks against management connections.
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>= 9.0.0, <= 9.0.5>= 9.1.0, <= 9.1.7>= 9.2.0, <= 9.2.5= 9.3.0CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the installed EdgeConnect SD-WAN Orchestrator versionAccess the Orchestrator admin interface or use the system command to retrieve the software version (for example, via 'show version' or through the web UI dashboard)Affected if The version number falls within 9.0.0-9.0.5, 9.1.0-9.1.7, 9.2.0-9.2.5, or 9.3.0
-
Locate the SSH host key files on the OrchestratorAccess the Orchestrator filesystem and navigate to the directory containing SSH host keys (typically /etc/ssh/ or similar on the appliance)Affected if Host key files exist on the system (this is required for the vulnerability to be present)
-
Inspect the SSH host keys for default valuesRead the contents of the SSH host key files (ssh_host_rsa_key, ssh_host_ecdsa_key, or ssh_host_ed25519_key) and examine the key fingerprint or modulusAffected if The host keys match the known shared default keys that were common across all installations (indicating they were never regenerated from the factory default)
-
Verify whether unique host keys were generated post-installationCompare the current host keys against what would be expected from a fresh unique key generation, or check if the keys have been regenerated since initial deploymentAffected if The host keys are identical to the default static keys distributed with the product rather than uniquely generated for this installation
The environment is affected if the installed Orchestrator version is within the affected ranges AND the SSH host keys are the shared default keys that were never regenerated to unique values.
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 dataUpdate to the fixed versions specified in the advisory and regenerate unique SSH host keys for each Orchestrator installation to replace the compromised shared keys.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37426 — 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-2023-37426 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