Replies: 3 comments 6 replies
-
Hi @teqoit joining a full text report would have been helpful, and maybe it would have include all the discovered issues. For all the CVE you're showing here, all are related to OpenSSL which is OpenSSL 1.1.1i in our MSI package. It is really outdated and you should know next 1.8 version would no more use this outdated OpenSSL DLL. And our nightly builds are still using an up-to-date OpenSSL DLL (actually the 3.2.1 version) as actually I adapted the build process to be able to build ourself the OpenSSL DLL from source. So we can use the latest release as soon as possible. An important point to know is by default OpenSSL in GLPI-Agent can only be used in a client context toward a well-known GLPI server if you configured your Of course, as this is eventually possible, we need to figure out the problem and, as I said, this is still addressed for next version regarding OpenSSL as we will use the latest possible OpenSSL version. But have you in the report some other CVE not related to OpenSSL ? Can you eventually provide a report for the latest nightly build ? Take it from there: https://nightly.glpi-project.org/glpi-agent/ |
Beta Was this translation helpful? Give feedback.
-
any update? |
Beta Was this translation helpful? Give feedback.
-
Hi @teqoit glpi-agent 1.8 was released last week and fixes most of your concerns. Anyway, some issues was reported regarding ssl support and as now it is fixed in nightly builds, I can understand how your VAPT tool reported was able to report zlib 1.2.11 was used. So can you use your tool on latest nightly build ? About the licensing issues, I still require more details. |
Beta Was this translation helpful? Give feedback.
-
Documentation & bug reporting acknowledgment
Yes, I read it
Describe your problem
we have done VAPT internally and its found some vulnerabilities.
and more
Beta Was this translation helpful? Give feedback.
All reactions