CVE-2013-4550

UnknownEPSS 2.22%

Last modified

CVE-2013-4550 is a vulnerability of currently unknown severity. Bip before 0.8.9, when running as a daemon, writes SSL handshake errors to an unexpected file descriptor that was previously associated with stderr before stderr has been closed, which allows remote attackers to write to other sockets and have an unspecified impact via a failed SSL handshake, a different vulnerability than CVE-2011-5268. NOTE: some sources originally mapped this CVE to two different types of issues; this CVE has since been SPLIT, producing CVE-2011-5268.. EPSS estimates a 2.22% chance of exploitation in the next 30 days.

Description

Bip before 0.8.9, when running as a daemon, writes SSL handshake errors to an unexpected file descriptor that was previously associated with stderr before stderr has been closed, which allows remote attackers to write to other sockets and have an unspecified impact via a failed SSL handshake, a different vulnerability than CVE-2011-5268. NOTE: some sources originally mapped this CVE to two different types of issues; this CVE has since been SPLIT, producing CVE-2011-5268.

Metrics

EPSS Probability
2.22%

80.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
FedoraprojectFedora18
FedoraprojectFedora19
FedoraprojectFedora20
DuckcorpBip<= 0.8.8
DuckcorpBip0.8.0
DuckcorpBip0.8.1
DuckcorpBip0.8.2
DuckcorpBip0.8.3
DuckcorpBip0.8.4
DuckcorpBip0.8.5
DuckcorpBip0.8.6
DuckcorpBip0.8.7

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2013-4550?
Bip before 0.8.9, when running as a daemon, writes SSL handshake errors to an unexpected file descriptor that was previously associated with stderr before stderr has been closed, which allows remote attackers to write to other sockets and have an unspecified impact via a failed SSL handshake, a different vulnerability than CVE-2011-5268. NOTE: some sources originally mapped this CVE to two different types of issues; this CVE has since been SPLIT, producing CVE-2011-5268.
How severe is CVE-2013-4550?
Severity scoring for CVE-2013-4550 is pending analysis. The EPSS model estimates a 2.22% probability of exploitation in the next 30 days.
How do I fix CVE-2013-4550?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2013-4550?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST