wazuh / wazuh-qa

Wazuh - Quality Assurance
GNU General Public License v2.0
64 stars 30 forks source link

CentOS 7: Analyze vulnerability discrepancies in the report between 4.7.3 and 4.8.0 #5119

Closed cborla closed 5 months ago

cborla commented 5 months ago
Platform From To
CentOS 7 4.7.3 4.8.0-beta4

We are tasked with performing a comprehensive analysis of vulnerability discrepancies reported between versions 4.7.3 and 4.8.0 in CentOS 7. This entails scrutinizing each vulnerability identified in the report, cross-referencing them with official sources such as the National Vulnerability Database (NVD), Canonical, Red Hat Security Advisories (RHSA), and other trusted sources.

To accomplish this, we will follow a systematic approach:

  1. Gathering Vulnerability List: We will compile a comprehensive list of vulnerabilities detected in versions 4.7.0 and 4.8.0. This list will be sourced from the provided report and any additional channels that may provide pertinent information. (Link)

  2. Package Inventory Examination: We will thoroughly examine the package inventory associated with the aforementioned versions to ensure accuracy in vulnerability identification and tracking.

  3. Verification with Official Sources: Each identified vulnerability will be meticulously compared with information available from official sources such as the NVD, Canonical, RHSA, and other relevant platforms. This step is crucial in validating the existence and severity of each vulnerability.

  4. Analysis and Documentation: We will document our findings in a structured manner, presenting a detailed analysis of each vulnerability and highlighting any variances or discrepancies encountered between the provided report and official sources.

  5. Compilation of Results: Based on our analysis, we will populate a comprehensive table detailing the results of our comparison. This table will serve as a reference point for understanding the status of each vulnerability and any deviations observed.

  6. Recommendations: Finally, we will provide recommendations based on our findings, including potential actions to address any identified vulnerabilities and mitigate associated risks effectively.

By adhering to this methodical approach, we aim to ensure thoroughness and accuracy in our analysis of vulnerability discrepancies between versions 4.7.0 and 4.8.0. This endeavor will contribute to enhancing the overall security posture of our system and bolstering our resilience against potential threats.

cborla commented 5 months ago

Issue Update

The analysis is still in progress:

Spreadsheet: link

After proceeding with the manual analysis, perform a filter using the ova provided by rhel-7-including-unpatched.oval.xml.bz2 filling in the state column with which we can get an idea of whether the vulnerability was well generated or not.

cborla commented 5 months ago

Issue Update

The analysis is still in progress:

Spreadsheet: link

nmkoremblum commented 5 months ago

Issue Update

The analysis is still in progress:

Vulnerabilities in 4.8.0, not reported in 4.7.3:
    4 failures.
    65 doubtful (Under investigation or undefined).
Vulnerabilities in 4.7.3, not reported in 4.8.0:
    171 failures.

Spreadsheet: link

After proceeding with the manual analysis, perform a filter using the ova provided by rhel-7-including-unpatched.oval.xml.bz2 filling in the state column with which we can get an idea of whether the vulnerability was well generated or not.

cborla commented 5 months ago

Issue Update

The analysis is still in progress:

Spreadsheet: link

Conclusion

We note that version 4.8.0 reports more vulnerabilities than version 4.7.3, which is correct, but all vulnerabilities listed as success in the 4.7.3 - 4.8.0 spreadsheet should have been reported by 4.8.0. understanding that there are 368 false negatives of 4.8.0.

sebasfalcone commented 5 months ago

False negatives (version with epoch)

All false negatives of packages in which its version contains an epoch have the same problem as described here:

It will be fixed here:

[!NOTE] These CVEs serve as an example:

  • CVE-2023-2828
  • CVE-2023-3341
  • CVE-2021-25214
  • CVE-2021-25215
  • CVE-2021-25220

CC: @Damian-Mangold

sebasfalcone commented 5 months ago

False negative (packages with no fix)

Packages that are affected by default are not being detected as such. This issue will be further investigated here:

Example (CVE-2019-19645)

This vulnerability affects: