Unfortunately, in addition to not being a developer I do not have an intimate understanding how how MS SQL 2019 actually functions, so I don't know what would go wrong if I simply swapped out that file with a new one manually (and there's no clear candidate for that anyways). The latest official version is 4.2.6 (LTS). Here’s how to get it: Option 1: Get the latest official version. See the FAQ for the Python versions supported by each version of Django. The last version to support Python 2.7 is Django 1.11 LTS. I suspect this is not just a drag-and-drop operation, as I'm sure the flagged file gets called by the application somehow. We recommend using the latest version of Python 3. The same site has a section of articles that seem to be geared towards how developers can use Apache2 (which seems to be what this file collection actually is) but I'm not a developer, just a systems manager. There's no installer, just a bunch of files. Unfortunately I don't know how to use it. It seems to be, specifically, the file log4j-1.2.17.jar that is implicated.Įvidently there is a version 2.17.1 available here: It causes two high-priority findings that I must get resolved. My vulnerability scanner recently flagged an unsupported installation of Apache Log4j in a version of MS SQL we just recently deployed (SQL 2019).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |