PatchTheCVElibgig0 vulnerabilities
Recent CVEs affecting libgig0 products. 4 tracked.
libgig0 has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-08-28. Highest priority: CVE-2017-12954 (score 50/100).
- CVE-2017-12954 MEDIUM 6.5 DOWNGRADE The gig::Region::GetSampleFromWavePool function in gig.cpp in libgig 4.0.0 allows remote attackers to cause a
- CVE-2017-12953 MEDIUM 6.5 DOWNGRADE The gig::Instrument::UpdateRegionKeyTable function in gig.cpp in libgig 4.0.0 allows remote attackers to cause
- CVE-2017-12952 MEDIUM 6.5 DOWNGRADE The LoadString function in helper.h in libgig 4.0.0 allows remote attackers to cause a denial of service (NULL
- CVE-2017-12951 MEDIUM 6.5 DOWNGRADE The gig::DimensionRegion::CreateVelocityTable function in gig.cpp in libgig 4.0.0 allows remote attackers to c
FAQ
How do I fix libgig0 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 libgig0 being exploited right now?
None of the tracked libgig0 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libgig0 CVE should I patch first?
CVE-2017-12954 currently ranks highest (50/100): The gig::Region::GetSampleFromWavePool function in gig.cpp in libgig 4.0.0 allows remote attackers to cause a .