Tenable Report Issue even after upgrading to correct Postgres version - Mailing list pgsql-bugs

From Kishore Isaac
Subject Tenable Report Issue even after upgrading to correct Postgres version
Date
Msg-id 4704eb478e1b4a7d967a9d7584b8c8af@GL-EXCHANGE02.loccioni.com
Whole thread Raw
Responses Re: Tenable Report Issue even after upgrading to correct Postgres version
List pgsql-bugs

To Whom It May Concern:

 

We were informed by a customer using Tenable reports that we needed to upgrade Postgres from 12.2 to 12.7 due to vulnerability issues. We have since upgraded to the requested version of Postgres (12.7) but the Tenable report scans still show that the version is 12.2. After reaching out the Tenable, we found that the version information is not updated in the system registry where Tenable is pulling the information from. Is there any resolution for this?

 

Below is the registry information:

 

 

And below this is proof that we upgraded the Postgres version:

 

 

Thanks,

 

Kishore Isaac

 

 

Phone                         301 477 7048

Web                            www.loccioni.com

________________________________________

PRIVACY

According to International Privacy Laws the information contained in this message is confidential and of exclusive use of the addressee(s). Should you receive this message by mistake, please delete it and send a written communication to privacy@loccioni.com

Please consider the environment before printing this email

 

Attachment

pgsql-bugs by date:

Previous
From: "Andrew J. Schorr"
Date:
Subject: pgdg-redhat-repo-42.0-20.noarch is missing pgdg14-source and pgdg13-source
Next
From: Bruce Momjian
Date:
Subject: Re: Tenable Report Issue even after upgrading to correct Postgres version