Forum Discussion
npgsql 4.0.10.0 not safe ?
Hi Flyn -Try creating an environment variable or system path to explicitly point to the latest Npgsql version installed on your system.You could also consult your IT team to ensure Power BI configuration files (e.g., pbix files) are updated to work with newer drivers.
By upgrading and configuring your connection carefully, you should be able to mitigate the risks without having to revert to vulnerable versions of Npgsql.
Npgsql - .NET Access to PostgreSQL | Npgsql Documentation
this may stem from the fact that certain applications or environments are configured to recognize only specific driver versions. While version 4.0.10 and earlier versions are considered vulnerable, installing a patched or later version of Npgsql (e.g., 4.1.x or higher) should resolve these vulnerabilities.
Hope this information helps.
Hi rajendraongole1 thanks for you answer. I already have both feature you mentionned "this includes ensuring encrypted connections, proper role-based access control in PostgreSQL,..." but i change my computer and when i try to access to my postgre data base it said to download a NPGSQL version 4.0.10 or a older version. The 4.0.10 version and every older version are considerate "vulnerable". i don't know if it will work if i can install a patched version
Hi Flyn -Try creating an environment variable or system path to explicitly point to the latest Npgsql version installed on your system.You could also consult your IT team to ensure Power BI configuration files (e.g., pbix files) are updated to work with newer drivers.
By upgrading and configuring your connection carefully, you should be able to mitigate the risks without having to revert to vulnerable versions of Npgsql.
Npgsql - .NET Access to PostgreSQL | Npgsql Documentation
this may stem from the fact that certain applications or environments are configured to recognize only specific driver versions. While version 4.0.10 and earlier versions are considered vulnerable, installing a patched or later version of Npgsql (e.g., 4.1.x or higher) should resolve these vulnerabilities.
Hope this information helps.
Ok. That mean despite of power bi indicate us to work with a "4.0.10 version or earlier", if i install a patched version it will work ?