Skip to main content
No exploitation reported

CVE-2015-7923

No exploitation reported by the sources we read.

  • Published2016-01-30
  • WeaknessCWE-310

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Westermo WeOS before 4.19.0 uses the same SSL private key across different customers' installations, which makes it easier for man-in-the-middle attackers to defeat cryptographic protection mechanisms by leveraging knowledge of a key.

Timeline

dates in UTC
  1. 2016-01-3012:59CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2015-7923?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2015-7923?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Westermo weos
BranchAffectedFixed in
4.18= 4.18.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-16-028-01A CISA1 known affected

    Westermo Industrial Switch Hard-coded Certificate Vulnerability (Update A)

    Westermo WeOS: <4.19.0

Full record on NVD

Fix

  1. Mitigation from the vendor CISA ICSA-16-028-01A · 1 productWestermo has released a patch that allows changing default certificates to custom certificates. Directions for changing certificates can be found in the WeOS Management Guide Section 7.1.8 or by contacting Westermo Support at +46 16 428000.
  2. Mitigation from the vendor CISA ICSA-16-028-01A · 1 productIn the meanwhile, users should follow the procedure below to mitigate the vulnerability: 1. Devices with WeOS versions older than 4.15.2 should be upgraded to the latest release in order to get the capability to replace the default web certificate. 2. Upload a custom certificate, preferably from an…
  3. Mitigation from the vendor CISA ICSA-16-028-01A · 1 productSelf-signed certificates should be avoided, because they provide a similar attack vector because the keys encrypting traffic are not established until after the first access of the device.
  4. Mitigation from the vendor CISA ICSA-16-028-01A · 1 productWeb access can either be disabled completely or allowed only from the most secure network as it reduces the exposure of this vulnerability to that network. The attacker must gain access to the more secure network in order to stage an attack.

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.09read 2026-10-23
  • NVDCVSS 2.09.3read 2026-10-23
  • NVDweakness (CWE)CWE-310read 2026-10-23
  • FIRST EPSSEPSS score1.2 %2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Published
2016-01-30
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2015-7923?

Westermo WeOS before 4.19.0 uses the same SSL private key across different customers' installations, which makes it easier for man-in-the-middle attackers to defeat cryptographic protection mechanisms by leveraging knowledge of a key.

Is CVE-2015-7923 actively exploited?

Active exploitation of CVE-2015-7923 has not been confirmed. Its EPSS score was 1.2% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2015-7923?

CVE-2015-7923 has a CVSS v3 base score of 9 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month