CVE-2013-0529

CVE-2013-0529 is a medium-severity vulnerability in Ibm Sterling Connect Direct User Interface with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-264.

Key facts

Description

The Browser in IBM Sterling Connect:Direct 1.4 before 1.4.0.11 and 1.5 through 1.5.0.1 does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.

Frequently asked questions

What is CVE-2013-0529?
The Browser in IBM Sterling Connect:Direct 1.4 before 1.4.0.11 and 1.5 through 1.5.0.1 does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.
How severe is CVE-2013-0529?
CVE-2013-0529 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2013-0529 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2013-0529?
CVE-2013-0529 primarily affects Ibm Sterling Connect Direct User Interface. In total, 8 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2013-0529?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2013-0529 published?
CVE-2013-0529 was published on 2013-06-21 and last updated on 2026-06-16.

References

Affected products (8)

More vulnerabilities in Ibm Sterling Connect Direct User Interface

All CVEs affecting Ibm Sterling Connect Direct User Interface →

Other CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities

Browse all CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities →