DBS3900 TDD LTE V100R003C00, V100R004C10 have a weak encryption algorithm security vulnerability.

published 2018-03-23 8y ago modified 2026-06-17 4mo ago also EUVD-2017-6782

cvss: 4.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits: 0; none known

DBS3900 TDD LTE V100R003C00, V100R004C10 have a weak encryption algorithm security vulnerability. DBS3900 TDD LTE supports SSL/TLS protocol negotiation using insecure encryption algorithms. If an insecure encryption algorithm is negotiated in the communication, an unauthenticated remote attacker can exploit this vulnerability to crack the encrypted data and cause information leakage.

Is CVE-2017-15326 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	4.3	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

Huawei Technologies Co., Ltd. DBS3900 TDD LTE

Classification

Weakness

CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

huawei.com /en/psirt/security-advisories/2018/huawei-sa-20180321-01-encryption-en
vendor-advisory

Sources

CVE List CVE-2017-15326
NVD CVE-2017-15326

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.