Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nucleus: [High] - 440056 #7

Closed
mcsaez2 opened this issue May 16, 2024 · 1 comment
Closed

Nucleus: [High] - 440056 #7

mcsaez2 opened this issue May 16, 2024 · 1 comment

Comments

@mcsaez2
Copy link

mcsaez2 commented May 16, 2024

Source: QUALYS
Description: CentOS has released security update for kernel to fix the vulnerabilities. Affected Products: centos 6

Impact: Successful exploitation allows attacker to compromise the system.

Target:
Asset name: 192.168.56.103 - IP: 192.168.56.103
Asset name: 192.168.56.146 - IP: 192.168.56.146

Solution: To resolve this issue, upgrade to the latest packages which contain a patch. Refer to CentOS advisory centos 6 (https://lists.centos.org/pipermail/centos-announce/2016-August/022053.html) for updates and patch information.
Patch:
Following are links for downloading patches to fix the vulnerabilities:
CESA-2016:1664: centos 6 (https://lists.centos.org/pipermail/centos-announce/2016-August/022053.html)

References:
QID: 440056
CVE: CVE-2016-5696, CVE-2021-42321, CVE-2017-15804
Category: CentOS
PCI Flagged: yes
Vendor References: CESA-2016:1664 centos 6
Bugtraq IDs: 91704

Severity: High
Exploitable: No
Date Discovered: 2021-12-12 10:43:00

Please see https://192.168.56.101/nucleus/public/app/index.php#vuln/130000004/NDQwMDU2/UVVBTFlT/false/false/MTMwMDAwMDA0/bWl0aWdhdGVk/true/false for more information on these vulnerabilities
Issue was manually created by Nucleus user: Nucleus User

@mcsaez2 mcsaez2 closed this as completed May 16, 2024
@mcsaez2
Copy link
Author

mcsaez2 commented May 16, 2024

By Nucleus Bot

Ticket was closed via a ticketing rule from Nucleus as new data was ingested.

All instances of this vulnerability on this ticket have been remediated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant