CTPView: HSTS not being enforced on CTPView server.

published 2021-10-19 5y ago modified 2026-06-17 4mo ago also EUVD-2021-2915

cvss: 7.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits: 0; none known

The Juniper Networks CTPView server is not enforcing HTTP Strict Transport Security (HSTS). HSTS is an optional response header which allows servers to indicate that content from the requested domain will only be served over HTTPS. The lack of HSTS may leave the system vulnerable to downgrade attacks, SSL-stripping man-in-the-middle attacks, and weakens cookie-hijacking protections. This issue affects Juniper Networks CTPView: 7.3 versions prior to 7.3R7; 9.1 versions prior to 9.1R3.

Patch / fix

fixed in 1

Juniper Networks CTPView 7.3R7, 9.1R3

Is CVE-2021-0296 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.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.4	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	5.8	AV:N/AC:M/Au:N/C:P/I:P/A:N

Affected products

Juniper Networks CTPView

Classification

Weakness

CWE-319 Cleartext Transmission of Sensitive Information

References

kb.juniper.net /JSA11210
vendor-advisory

Sources

CVE List CVE-2021-0296
NVD CVE-2021-0296

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.