stream control transmission protocol vulnerabilities and fixes

Recent CVEs affecting stream control transmission protocol, with upgrade or downgrade steps. 3 tracked.

Also searched as: streamcontroltransmissionprotocol.

stream control transmission protocol has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2006-05-09. Highest priority: CVE-2006-2275 (score 59/100).

• CVE-2006-2275 HIGH 7.5 UPGRADE MITIGATE Linux SCTP (lksctp) before 2.6.17 allows remote attackers to cause a denial of service (deadlock) via a large
• CVE-2006-2274 MEDIUM 5.0 DOWNGRADE Linux SCTP (lksctp) before 2.6.17 allows remote attackers to cause a denial of service (infinite recursion and
• CVE-2006-2272 HIGH 7.8 UPGRADE Linux SCTP (lksctp) before 2.6.17 allows remote attackers to cause a denial of service (kernel panic) via inco

FAQ

How do I fix stream control transmission protocol vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is stream control transmission protocol being exploited right now?

None of the tracked stream control transmission protocol CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which stream control transmission protocol CVE should I patch first?

CVE-2006-2275 currently ranks highest (59/100): Linux SCTP (lksctp) before 2.6.17 allows remote attackers to cause a denial of service (deadlock) via a large .

RSS feed for stream control transmission protocol · ← Back to latest CVEs