У меня есть таблица exel приведенная ниже, тебе нужно написать программы python которая правильно сформирует информацию по столбцам с соотвествующими названиями например cve будет в cve, сейчас там полный разброс по строкам, лишнюю информацию можно удалять
Hostname 	Package	Version	CVE	Column5	Column6	Column7	Column8	Column9	Column10	Column11	Column12	Column13	Column14	Column15	Column16	Column17	Column18	Column19	Column20	Column21
p-sedv3-rosprirodnadzor-web1	apache-commons-lang3	3.7-3.module_el8.0.0+39+6a9b6e22	In Apache Maven maven-shared-utils prior to version 3.3.3, the Commandline class can emit double-quoted strings without proper escaping, allowing shell injection attacks.	High	CVE-2022-29599															
p-sedv3-rosprirodnadzor-storage1	bash	4.2.46-34.el7	An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support saved UID" functionality	 the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin	 which can be a shared object that calls setuid() and therefore regains privileges. However	 binaries running with an effective UID of 0 are unaffected."	High	CVE-2019-18276												
p-sedv3-rosprirodnadzor-web1	bind-export-libs	32:9.11.20-5.el8	If a server hosts a zone containing a KEY" Resource Record	 or a resolver DNSSEC-validates a "KEY" Resource Record from a DNSSEC-signed domain in cache	 a client can exhaust resolver CPU resources by sending a stream of SIG(0) signed requests. This issue affects BIND 9 versions 9.0.0 through 9.11.37	 9.16.0 through 9.16.50	 9.18.0 through 9.18.27	 9.19.0 through 9.19.24	 9.9.3-S1 through 9.11.37-S1	 9.16.8-S1 through 9.16.49-S1	 and 9.18.11-S1 through 9.18.27-S1."	High	CVE-2024-1975							
p-sedv3-rosprirodnadzor-orders	container-selinux	2:2.167.0-1.module_el8.5.0+911+f19012f9	Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. var a = {{.}}")	 since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix	 Template.Parse returns an Error when it encounters templates like this	 with an ErrorCode of value 12. This ErrorCode is currently unexported	 but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1	 with the caveat that backticks will now be escaped. This should be used with caution."	Critical	CVE-2023-24538										
p-sedv3-rosprirodnadzor-orders	container-selinux	2:2.167.0-1.module_el8.5.0+911+f19012f9	A denial of service is possible from excessive resource consumption in net/http and mime/multipart. Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. ReadForm takes a maxMemory parameter, and is documented as storing up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However	 ReadForm did not properly account for all memory consumed by a parsed form	 such as map entry overhead	 part names	 and MIME headers	 permitting a maliciously crafted form to consume well over 10MB. In addition	 ReadForm contained no limit on the number of disk files created	 permitting a relatively small request body to create a large number of disk temporary files. With fix	 ReadForm now properly accounts for various forms of memory overhead	 and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous. In addition	 ReadForm now creates at most one on-disk temporary file	 combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states	 "If stored on disk	 the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part	 due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct. Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader."	High	CVE-2022-41725	
p-sedv3-rosprirodnadzor-orders	platform-python	3.6.8-41.el8	A flaw was found in python. In algorithms with quadratic time complexity using non-binary bases, when using int(text")	 a system could take 50ms to parse an int string with 100	000 digits and 5s for 1	0	000 digits (float	 decimal	 int.from_bytes()	 and int() for binary bases 2	4	8	16	 and 32 are not affected). The highest threat from this vulnerability is to system availability."	High	CVE-2020-10735				
p-sedv3-rosprirodnadzor-ocr	python3-bind	32:9.11.20-5.el8_3.1	Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the KeyTrap" issue. One of the concerns is that	 when there is a zone with many DNSKEY and RRSIG records	 the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records."	High	CVE-2023-50387