Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2016-6027
Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Description
The Configuration Manager in IBM Sterling Secure Proxy (SSP) 3.4.2 before 3.4.2.0 iFix 8 and 3.4.3 before 3.4.3.0 iFix 1 does not enable the HSTS protection mechanism, which makes it easier for remote attackers to obtain sensitive information or modify data by leveraging use of HTTP.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
IBM Sterling Secure Proxy 信息泄露漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
IBM Sterling Secure Proxy(SSP)是美国IBM公司的一个基于非保护区(DMZ)的应用程序代理,可保护来自公共因特网的文件传输。Configuration Manager是其中的一个配置管理组件。 IBM SSP中的Configuration Manager中存在信息泄露漏洞,该漏洞源于程序没有正确启用HTTP Strict Transport Security(HSTS)保护机制。攻击者可利用该漏洞获取敏感信息或修改数据。以下版本受到影响:IBM Sterling Secure
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
VendorProductAffected VersionsCPESubscribe
-n/a n/a -
II. Public POCs for CVE-2016-6027
#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC
III. Intelligence Information for CVE-2016-6027
Please Login to view more intelligence information
IV. Related Vulnerabilities
V. Comments for CVE-2016-6027

No comments yet


Leave a comment