/
2024.xml
1867 lines (1814 loc) · 64.9 KB
/
2024.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<vuln vid="979dc373-d27d-11ee-8b84-b42e991fc52e">
<topic>suricata -- multiple vulnerabilities</topic>
<affects>
<package>
<name>suricata</name>
<range><lt>7.0.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Suricata team reports:</p>
<blockquote cite="https://suricata.io/2024/02/08/suricata-7-0-3-and-6-0-16-released/">
<p>Multiple vulnerabilities fixed in the last release of suricata.</p>
</blockquote>
<p>No details have been disclosed yet</p>
</body>
</description>
<references>
<cvename>CVE-2024-23839</cvename>
<cvename>CVE-2024-23836</cvename>
<cvename>CVE-2024-23835</cvename>
<cvename>CVE-2024-24568</cvename>
<cvename>CVE-2024-23837</cvename>
</references>
<dates>
<discovery>2024-01-22</discovery>
<entry>2024-02-23</entry>
</dates>
</vuln>
<vuln vid="80ad6d6c-b398-457f-b88f-bf6be0bbad44">
<topic>electron27 -- multiple vulnerabilities</topic>
<affects>
<package>
<name>electron27</name>
<range><lt>27.3.3</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Electron developers report:</p>
<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.3">
<p>This update fixes the following vulnerability:</p>
<ul>
<li>Security: backported fix for CVE-2024-1283.</li>
<li>Security: backported fix for CVE-2024-1284.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-1283</cvename>
<url>https://github.com/advisories/GHSA-7mgj-p9v3-3vxr</url>
<cvename>CVE-2024-1284</cvename>
<url>https://github.com/advisories/GHSA-pf89-rhhw-xmhp</url>
</references>
<dates>
<discovery>2024-02-21</discovery>
<entry>2024-02-23</entry>
</dates>
</vuln>
<vuln vid="03bf5157-d145-11ee-acee-001b217b3468">
<topic>Gitlab -- Vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>16.9.0</ge><lt>16.9.1</lt></range>
<range><ge>16.8.0</ge><lt>16.8.3</lt></range>
<range><ge>11.3.0</ge><lt>16.7.6</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/releases/2024/02/21/security-release-gitlab-16-9-1-released/">
<p>Stored-XSS in user's profile page</p>
<p>User with "admin_group_members" permission can invite other groups to gain owner access</p>
<p>ReDoS issue in the Codeowners reference extractor</p>
<p>LDAP user can reset password using secondary email and login using direct authentication</p>
<p>Bypassing group ip restriction settings to access environment details of projects through Environments/Operations Dashboard</p>
<p>Users with the Guest role can change Custom dashboard projects settings for projects in the victim group</p>
<p>Group member with sub-maintainer role can change title of shared private deploy keys</p>
<p>Bypassing approvals of CODEOWNERS</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-1451</cvename>
<cvename>CVE-2023-6477</cvename>
<cvename>CVE-2023-6736</cvename>
<cvename>CVE-2024-1525</cvename>
<cvename>CVE-2023-4895</cvename>
<cvename>CVE-2024-0861</cvename>
<cvename>CVE-2023-3509</cvename>
<cvename>CVE-2024-0410</cvename>
<url>https://about.gitlab.com/releases/2024/02/21/security-release-gitlab-16-9-1-released/</url>
</references>
<dates>
<discovery>2024-02-21</discovery>
<entry>2024-02-22</entry>
</dates>
</vuln>
<vuln vid="e15ba624-cca8-11ee-84ca-b42e991fc52e">
<topic>powerdns-recursor -- Multiple Vulnerabilities</topic>
<affects>
<package>
<name>powerdns-recursor</name>
<range><lt>5.0.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>cve@mitre.org reports:</p>
<blockquote cite="https://access.redhat.com/security/cve/CVE-2023-50868">
<p>CVE-2023-50868: The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155
when RFC 9276 guidance is skipped) allows remote attackers to cause
a denial of service (CPU consumption for SHA-1 computations) via
DNSSEC responses in a random subdomain attack, aka the "NSEC3"
issue. The RFC 5155 specification implies that an algorithm must
perform thousands of iterations of a hash function in certain
situations.</p>
<p>CVE-2023-50387: 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.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2023-50868</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2023-50868</url>
<cvename>CVE-2023-50387</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2023-50387</url>
</references>
<dates>
<discovery>2024-02-14</discovery>
<entry>2024-02-16</entry>
</dates>
</vuln>
<vuln vid="c97a4ecf-cc25-11ee-b0ee-0050569f0b83">
<topic>nginx-devel -- Multiple Vulnerabilities in HTTP/3</topic>
<affects>
<package>
<name>nginx-devel</name>
<range><ge>1.25.0</ge><lt>1.25.4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The nginx development team reports:</p>
<blockquote cite="http://nginx.org/en/security_advisories.html">
<p>When using HTTP/3 a segmentation fault might occur in a
worker process while processing a specially crafted QUIC session.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-24989</cvename>
<cvename>CVE-2024-24990</cvename>
</references>
<dates>
<discovery>2024-02-14</discovery>
<entry>2024-02-15</entry>
</dates>
</vuln>
<vuln vid="46a29f83-cb47-11ee-b609-002590c1f29c">
<topic>FreeBSD -- jail(2) information leak</topic>
<affects>
<package>
<name>FreeBSD-kernel</name>
<range><ge>14.0</ge><lt>14.0_5</lt></range>
<range><ge>13.2</ge><lt>13.2_10</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>The jail(2) system call has not limited a visiblity of allocated
TTYs (the kern.ttys sysctl). This gives rise to an information
leak about processes outside the current jail.</p>
<h1>Impact:</h1>
<p>Attacker can get information about TTYs allocated on the host
or in other jails. Effectively, the information printed by "pstat
-t" may be leaked.</p>
</body>
</description>
<references>
<cvename>CVE-2024-25941</cvename>
<freebsdsa>SA-24:02.tty</freebsdsa>
</references>
<dates>
<discovery>2024-02-14</discovery>
<entry>2024-02-14</entry>
</dates>
</vuln>
<vuln vid="c62285cb-cb46-11ee-b609-002590c1f29c">
<topic>FreeBSD -- bhyveload(8) host file access</topic>
<affects>
<package>
<name>FreeBSD</name>
<range><ge>14.0</ge><lt>14.0_5</lt></range>
<range><ge>13.2</ge><lt>13.2_10</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<h1>Problem Description:</h1>
<p>`bhyveload -h <host-path>` may be used to grant loader access
to the <host-path> directory tree on the host. Affected versions
of bhyveload(8) do not make any attempt to restrict loader's access
to <host-path>, allowing the loader to read any file the host user
has access to.</p>
<h1>Impact:</h1>
<p>In the bhyveload(8) model, the host supplies a userboot.so to
boot with, but the loader scripts generally come from the guest
image. A maliciously crafted script could be used to exfiltrate
sensitive data from the host accessible to the user running
bhyhveload(8), which is often the system root.</p>
</body>
</description>
<references>
<cvename>CVE-2024-25940</cvename>
<freebsdsa>SA-24:01.bhyveload</freebsdsa>
</references>
<dates>
<discovery>2024-02-14</discovery>
<entry>2024-02-14</entry>
</dates>
</vuln>
<vuln vid="4edbea45-cb0c-11ee-86bb-a8a1599412c6">
<topic>chromium -- security fix</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>121.0.6167.184</lt></range>
</package>
<package>
<name>ungoogled-chromium</name>
<range><lt>121.0.6167.184</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_13.html">
<p>This update includes 1 security fix.</p>
</blockquote>
</body>
</description>
<references>
<url>https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_13.html</url>
</references>
<dates>
<discovery>2024-02-13</discovery>
<entry>2024-02-14</entry>
</dates>
</vuln>
<vuln vid="21a854cc-cac1-11ee-b7a7-353f1e043d9a">
<topic>DNSSEC validators -- denial-of-service/CPU exhaustion from KeyTrap and NSEC3 vulnerabilities</topic>
<affects>
<package>
<name>bind916</name>
<range><lt>9.16.48</lt></range>
</package>
<package>
<name>bind918</name>
<range><lt>9.18.24</lt></range>
</package>
<package>
<name>bind9-devel</name>
<range><lt>9.19.21</lt></range>
</package>
<package>
<name>dnsmasq</name>
<range><lt>2.90</lt></range>
</package>
<package>
<name>dnsmasq-devel</name>
<range><lt>2.90</lt></range>
</package>
<package>
<name>powerdns-recursor</name>
<range><lt>5.0.2</lt></range>
</package>
<package>
<name>unbound</name>
<range><lt>1.19.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Simon Kelley reports:</p>
<blockquote cite="https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html">
<p>If DNSSEC validation is enabled, then an attacker who can force a
DNS server to validate a specially crafted signed domain can use a
lot of CPU in the validator. This only affects dnsmasq installations
with DNSSEC enabled.</p>
</blockquote>
<p>Stichting NLnet Labs reports:</p>
<blockquote cite="https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/">
<p>
The KeyTrap [CVE-2023-50387] vulnerability works by using a
combination of Keys (also colliding Keys), Signatures and number of
RRSETs on a malicious zone. Answers from that zone can force a
DNSSEC validator down a very CPU intensive and time costly
validation path.
</p>
<p>
The NSEC3 [CVE-2023-50868] vulnerability uses specially crafted responses on a
malicious zone with multiple NSEC3 RRSETs to force a DNSSEC
validator down a very CPU intensive and time costly NSEC3 hash
calculation path.
</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2023-50387</cvename>
<cvename>CVE-2023-50868</cvename>
<url>https://kb.isc.org/docs/cve-2023-50387</url>
<url>https://kb.isc.org/docs/cve-2023-50868</url>
<url>https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html</url>
<url>https://blog.powerdns.com/2024/02/13/powerdns-recursor-4-8-6-4-9-3-5-0-2-released</url>
<url>https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/</url>
</references>
<dates>
<discovery>2024-02-06</discovery>
<entry>2024-02-13</entry>
</dates>
</vuln>
<vuln vid="cbfc1591-c8c0-11ee-b45a-589cfc0f81b0">
<topic>phpmyfaq -- multiple vulnerabilities</topic>
<affects>
<package>
<name>phpmyfaq-php81</name>
<name>phpmyfaq-php82</name>
<name>phpmyfaq-php83</name>
<range><lt>3.2.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>phpMyFAQ team reports:</p>
<blockquote cite="https://www.phpmyfaq.de/security/advisory-2024-02-05">
<p>phpMyFAQ doesn't implement sufficient checks to avoid XSS when
storing on attachments filenames. The 'sharing FAQ' functionality
allows any unauthenticated actor to misuse the phpMyFAQ application
to send arbitrary emails to a large range of targets. phpMyFAQ's
user removal page allows an attacker to spoof another user's
detail, and in turn make a compelling phishing case for removing
another user's account.</p>
</blockquote>
</body>
</description>
<references>
<url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-7m8g-fprr-47fx</url>
<url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-9hhf-xmcw-r3xg</url>
<url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6648-6g96-mg35</url>
</references>
<dates>
<discovery>2024-02-05</discovery>
<entry>2024-02-11</entry>
</dates>
</vuln>
<vuln vid="f161a5ad-c9bd-11ee-b7a7-353f1e043d9a">
<topic>openexr -- Heap Overflow in Scanline Deep Data Parsing</topic>
<affects>
<package>
<name>openexr</name>
<range><lt>3.1.12</lt></range>
<range><ge>3.2.0</ge><lt>3.2.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Austin Hackers Anonymous report:</p>
<blockquote cite="https://takeonme.org/cves/CVE-2023-5841.html">
<p>Due to a failure in validating the number of scanline samples of a OpenEXR file containing deep scanline data, Academy Software Foundation OpenEXR image parsing library version 3.2.1 and prior is susceptible to a heap-based buffer overflow vulnerability.</p>
</blockquote>
<blockquote cite="https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.2.2">
<p>[...] it is in a routine that is predominantly used for development and
testing. It is not likely to appear in production code.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2023-5841</cvename>
<url>https://takeonme.org/cves/CVE-2023-5841.html</url>
<url>https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.2.2</url>
</references>
<dates>
<discovery>2023-10-26</discovery>
<entry>2024-02-12</entry>
</dates>
</vuln>
<vuln vid="388eefc0-c93f-11ee-92ce-4ccc6adda413">
<topic>readstat -- Heap buffer overflow in readstat_convert</topic>
<affects>
<package>
<name>readstat</name>
<range><lt>1.1.9</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Google reports:</p>
<blockquote cite="https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33991">
<p>A heap buffer overflow exists in readstat_convert.</p>
</blockquote>
</body>
</description>
<references>
<url>https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33991</url>
<url>https://osv.dev/vulnerability/OSV-2021-732</url>
<url>https://github.com/WizardMac/ReadStat/issues/285</url>
</references>
<dates>
<discovery>2021-05-05</discovery>
<entry>2024-02-12</entry>
</dates>
</vuln>
<vuln vid="cb22a9a6-c907-11ee-8d1c-40b034429ecf">
<topic>p5-Spreadsheet-ParseExcel -- Remote Code Execution Vulnerability</topic>
<affects>
<package>
<name>p5-Spreadsheet-ParseExcel</name>
<range><lt>0.66</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Spreadsheet-ParseExcel reports:</p>
<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2023-7101">
<p>
Spreadsheet::ParseExcel version 0.65 is a Perl module used for parsing Excel files.
Spreadsheet::ParseExcel is vulnerable to an arbitrary code execution (ACE) vulnerability
due to passing unvalidated input from a file into a string-type eval "eval".
Specifically, the issue stems from the evaluation of Number format strings
(not to be confused with printf-style format strings) within the Excel parsing logic.
</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2023-7101</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2023-7101</url>
</references>
<dates>
<discovery>2023-12-29</discovery>
<entry>2024-02-11</entry>
</dates>
</vuln>
<vuln vid="19e6dd1b-c6a5-11ee-9cd0-6cc21735f730">
<topic>postgresql-server -- non-owner REFRESH MATERIALIZED VIEW CONCURRENTLY executes arbitrary SQL</topic>
<affects>
<package>
<name>postgresql-server</name>
<range><lt>15.6</lt></range>
<range><lt>14.11</lt></range>
<range><lt>13.14</lt></range>
<range><lt>12.18</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>PostgreSQL Project reports:</p>
<blockquote cite="https://www.postgresql.org/support/security/CVE-2024-0985/">
<p>
One step of a concurrent refresh command was run under
weak security restrictions. If a materialized view's
owner could persuade a superuser or other
high-privileged user to perform a concurrent refresh on
that view, the view's owner could control code executed
with the privileges of the user running REFRESH. The fix
for the vulnerability makes is so that all
user-determined code is run as the view's owner, as
expected.
</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-0985</cvename>
<url>https://www.postgresql.org/support/security/CVE-2024-0985/</url>
</references>
<dates>
<discovery>2024-02-08</discovery>
<entry>2024-02-08</entry>
</dates>
</vuln>
<vuln vid="6b2cba6a-c6a5-11ee-97d0-001b217b3468">
<topic>Gitlab -- vulnerabilities</topic>
<affects>
<package>
<name>gitlab-ce</name>
<range><ge>16.8.0</ge><lt>16.8.2</lt></range>
<range><ge>16.7.0</ge><lt>16.7.5</lt></range>
<range><ge>13.3.0</ge><lt>16.6.7</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Gitlab reports:</p>
<blockquote cite="https://about.gitlab.com/releases/2024/02/07/security-release-gitlab-16-8-2-released/">
<p>Restrict group access token creation for custom roles</p>
<p>Project maintainers can bypass group's scan result policy block_branch_modification setting</p>
<p>ReDoS in CI/CD Pipeline Editor while verifying Pipeline syntax</p>
<p>Resource exhaustion using GraphQL vulnerabilitiesCountByDay</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-1250</cvename>
<cvename>CVE-2023-6840</cvename>
<cvename>CVE-2023-6386</cvename>
<cvename>CVE-2024-1066</cvename>
<url>https://about.gitlab.com/releases/2024/02/07/security-release-gitlab-16-8-2-released/</url>
</references>
<dates>
<discovery>2024-02-07</discovery>
<entry>2024-02-08</entry>
</dates>
</vuln>
<vuln vid="33ba2241-c68e-11ee-9ef3-001999f8d30b">
<topic>Composer -- Code execution and possible privilege escalation</topic>
<affects>
<package>
<name>php81-composer</name>
<range><lt>2.7.0</lt></range>
</package>
<package>
<name>php82-composer</name>
<range><lt>2.7.0</lt></range>
</package>
<package>
<name>php83-composer</name>
<range><lt>2.7.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Copmposer reports:</p>
<blockquote cite="https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h">
<p>Code execution and possible privilege escalation via
compromised InstalledVersions.php or installed.php.</p>
<p>Several files within the local working directory are
included during the invocation of Composer and in the
context of the executing user.</p>
<p>As such, under certain conditions arbitrary code
execution may lead to local privilege escalation, provide
lateral user movement or malicious code execution when
Composer is invoked within a directory with tampered
files.</p>
<p>All Composer CLI commands are affected, including
composer.phar's self-update.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-24821</cvename>
<url>https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h</url>
</references>
<dates>
<discovery>2024-02-08</discovery>
<entry>2024-02-08</entry>
</dates>
</vuln>
<vuln vid="43768ff3-c683-11ee-97d0-001b217b3468">
<topic>Libgit2 -- multiple vulnerabilities</topic>
<affects>
<package>
<name>eza</name>
<range><lt>0.18.2</lt></range>
</package>
<package>
<name>libgit2</name>
<range><ge>1.7.0</ge><lt>1.7.2</lt></range>
<range><lt>1.6.5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Git community reports:</p>
<blockquote cite="https://github.com/libgit2/libgit2/releases/tag/v1.7.2">
<p>A bug in git_revparse_single is fixed that could have caused the function to enter an infinite loop given well-crafted inputs, potentially causing a Denial of Service attack in the calling application</p>
<p>A bug in git_revparse_single is fixed that could have caused the function to enter an infinite loop given well-crafted inputs, potentially causing a Denial of Service attack in the calling application</p>
<p>A bug in the smart transport negotiation could have caused an out-of-bounds read when a remote server did not advertise capabilities</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-24577</cvename>
<url>https://github.com/libgit2/libgit2/releases/tag/v1.7.2</url>
</references>
<dates>
<discovery>2024-02-06</discovery>
<entry>2024-02-08</entry>
<modified>2024-02-14</modified>
</dates>
</vuln>
<vuln vid="19047673-c680-11ee-86bb-a8a1599412c6">
<topic>chromium -- multiple security fixes</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>121.0.6167.160</lt></range>
</package>
<package>
<name>ungoogled-chromium</name>
<range><lt>121.0.6167.160</lt></range>
</package>
<package>
<name>qt5-webengine</name>
<range><lt>5.15.16.p5_5</lt></range>
</package>
<package>
<name>qt6-webengine</name>
<range><lt>6.6.1_5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop.html">
<p>This update includes 3 security fixes:</p>
<ul>
<li>[41494539] High CVE-2024-1284: Use after free in Mojo. Reported by Anonymous on 2024-01-25</li>
<li>[41494860] High CVE-2024-1283: Heap buffer overflow in Skia. Reported by Jorge Buzeti (@r3tr074) on 2024-01-25</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-1284</cvename>
<cvename>CVE-2024-1283</cvename>
<url>https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop.html</url>
</references>
<dates>
<discovery>2024-02-06</discovery>
<entry>2024-02-08</entry>
</dates>
</vuln>
<vuln vid="68ae70c5-c5e5-11ee-9768-08002784c58d">
<topic>clamav -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>clamav</name>
<range><lt>1.2.2,1</lt></range>
</package>
<package>
<name>clamav-lts</name>
<range><lt>1.0.5,1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The ClamAV project reports:</p>
<blockquote cite="https://blog.clamav.net/2023/11/clamav-130-122-105-released.html">
<dl>
<dt>CVE-2024-20290</dt>
<dd>
A vulnerability in the OLE2 file format parser of ClamAV
could allow an unauthenticated, remote attacker to cause
a denial of service (DoS) condition on an affected
device. This vulnerability is due to an incorrect check
for end-of-string values during scanning, which may
result in a heap buffer over-read. An attacker could
exploit this vulnerability by submitting a crafted file
containing OLE2 content to be scanned by ClamAV on an
affected device. A successful exploit could allow the
attacker to cause the ClamAV scanning process to
terminate, resulting in a DoS condition on the affected
software and consuming available system resources.
</dd>
<dt>CVE-2024-20328</dt>
<dd>
Fixed a possible command injection vulnerability in the
"VirusEvent" feature of ClamAV's ClamD
service. To fix this issue, we disabled the '%f' format
string parameter. ClamD administrators may continue to
use the `CLAM_VIRUSEVENT_FILENAME` environment variable,
instead of '%f'. But you should do so only from within
an executable, such as a Python script, and not directly
in the clamd.conf "VirusEvent" command.
</dd>
</dl>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-20290</cvename>
<cvename>CVE-2024-20328</cvename>
<url>https://blog.clamav.net/2023/11/clamav-130-122-105-released.html</url>
</references>
<dates>
<discovery>2024-02-07</discovery>
<entry>2024-02-07</entry>
</dates>
</vuln>
<vuln vid="e0f6215b-c59e-11ee-a6db-080027a5b8e9">
<topic>Django -- multiple vulnerabilities</topic>
<affects>
<package>
<name>py39-django32</name>
<name>py310-django32</name>
<name>py311-django32</name>
<range><lt>3.2.24</lt></range>
</package>
<package>
<name>py39-django42</name>
<name>py310-django42</name>
<name>py311-django42</name>
<range><lt>4.2.8</lt></range>
</package>
<package>
<name>py311-django50</name>
<range><lt>5.0.2</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Django reports:</p>
<blockquote cite="https://www.djangoproject.com/weblog/2024/feb/06/security-releases/">
<p>CVE-2024-24680:Potential denial-of-service in intcomma template filter.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-24680</cvename>
<url>https://www.djangoproject.com/weblog/2024/feb/06/security-releases/</url>
</references>
<dates>
<discovery>2024-01-09</discovery>
<entry>2024-02-07</entry>
</dates>
</vuln>
<vuln vid="dc9e5237-c197-11ee-86bb-a8a1599412c6">
<topic>chromium -- multiple security fixes</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>121.0.6167.139</lt></range>
</package>
<package>
<name>ungoogled-chromium</name>
<range><lt>121.0.6167.139</lt></range>
</package>
<package>
<name>qt5-webengine</name>
<range><lt>5.15.16.p5_5</lt></range>
</package>
<package>
<name>qt6-webengine</name>
<range><lt>6.6.1_5</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_30.html">
<p>This update includes 4 security fixes:</p>
<ul>
<li>[1511567] High CVE-2024-1060: Use after free in Canvas. Reported by Anonymous on 2023-12-14</li>
<li>[1514777] High CVE-2024-1059: Use after free in WebRTC. Reported by Cassidy Kim(@cassidy6564) on 2023-12-29</li>
<li>[1511085] High CVE-2024-1077: Use after free in Network. Reported by Microsoft Security Research Center on 2023-12-13</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-1060</cvename>
<cvename>CVE-2024-1059</cvename>
<cvename>CVE-2024-1077</cvename>
<url>https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_30.html</url>
</references>
<dates>
<discovery>2024-01-30</discovery>
<entry>2024-02-02</entry>
</dates>
</vuln>
<vuln vid="72d6d757-c197-11ee-86bb-a8a1599412c6">
<topic>chromium -- multiple security fixes</topic>
<affects>
<package>
<name>chromium</name>
<range><lt>121.0.6167.85</lt></range>
</package>
<package>
<name>ungoogled-chromium</name>
<range><lt>121.0.6167.85</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Chrome Releases reports:</p>
<blockquote cite="https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html">
<p>This update includes 17 security fixes:</p>
<ul>
<li>[1484394] High CVE-2024-0812: Inappropriate implementation in Accessibility. Reported by Anonymous on 2023-09-19</li>
<li>[1504936] High CVE-2024-0808: Integer underflow in WebUI. Reported by Lyra Rebane (rebane2001) on 2023-11-24</li>
<li>[1496250] Medium CVE-2024-0810: Insufficient policy enforcement in DevTools. Reported by Shaheen Fazim on 2023-10-26</li>
<li>[1463935] Medium CVE-2024-0814: Incorrect security UI in Payments. Reported by Muneaki Nishimura (nishimunea) on 2023-07-11</li>
<li>[1477151] Medium CVE-2024-0813: Use after free in Reading Mode. Reported by @retsew0x01 on 2023-08-30</li>
<li>[1505176] Medium CVE-2024-0806: Use after free in Passwords. Reported by 18楼梦想改造家 on 2023-11-25</li>
<li>[1514925] Medium CVE-2024-0805: Inappropriate implementation in Downloads. Reported by Om Apip on 2024-01-01</li>
<li>[1515137] Medium CVE-2024-0804: Insufficient policy enforcement in iOS Security UI. Reported by Narendra Bhati of Suma Soft Pvt. Ltd. Pune (India) on 2024-01-03</li>
<li>[1494490] Low CVE-2024-0811: Inappropriate implementation in Extensions API. Reported by Jann Horn of Google Project Zero on 2023-10-21</li>
<li>[1497985] Low CVE-2024-0809: Inappropriate implementation in Autofill. Reported by Ahmed ElMasry on 2023-10-31</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-0812</cvename>
<cvename>CVE-2024-0808</cvename>
<cvename>CVE-2024-0810</cvename>
<cvename>CVE-2024-0814</cvename>
<cvename>CVE-2024-0813</cvename>
<cvename>CVE-2024-0806</cvename>
<cvename>CVE-2024-0805</cvename>
<cvename>CVE-2024-0804</cvename>
<cvename>CVE-2024-0811</cvename>
<cvename>CVE-2024-0809</cvename>
<url>https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html</url>
</references>
<dates>
<discovery>2024-01-23</discovery>
<entry>2024-02-02</entry>
</dates>
</vuln>
<vuln vid="13a8c4bf-cb2b-48ec-b49c-a3875c72b3e8">
<topic>electron{26,27,28} -- Use after free in Web Audio</topic>
<affects>
<package>
<name>electron26</name>
<range><lt>26.6.8</lt></range>
</package>
<package>
<name>electron27</name>
<range><lt>27.3.1</lt></range>
</package>
<package>
<name>electron28</name>
<range><lt>28.2.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Electron developers reports:</p>
<blockquote cite="https://github.com/electron/electron/releases/tag/v26.6.8">
<p>This update fixes the following vulnerability:</p>
<ul>
<li>Security: backported fix for CVE-2024-0807.</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-0807</cvename>
<url>https://github.com/advisories/GHSA-hjm7-v5pw-x89r</url>
</references>
<dates>
<discovery>2024-01-31</discovery>
<entry>2024-02-01</entry>
</dates>
</vuln>
<vuln vid="bbcb1584-c068-11ee-bdd6-4ccc6adda413">
<topic>qt6-webengine -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>qt5-webengine</name>
<range><lt>5.15.16.p5_5</lt></range>
</package>
<package>
<name>qt6-webengine</name>
<range><lt>6.6.1_4</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>Qt qtwebengine-chromium repo reports:</p>
<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=112-based">
<p>Backports for 3 security bugs in Chromium:</p>
<ul>
<li>[1505080] High CVE-2024-0807: Use after free in WebAudio</li>
<li>[1504936] Critical CVE-2024-0808: Integer underflow in WebUI</li>
<li>[1496250] Medium CVE-2024-0810: Insufficient policy enforcement in DevTools</li>
</ul>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-0807</cvename>
<cvename>CVE-2024-0808</cvename>
<cvename>CVE-2024-0810</cvename>
<url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=112-based</url>
</references>
<dates>
<discovery>2024-01-30</discovery>
<entry>2024-01-31</entry>
</dates>
</vuln>
<vuln vid="10dee731-c069-11ee-9190-84a93843eb75">
<topic>OpenSSL -- Multiple vulnerabilities</topic>
<affects>
<package>
<name>openssl</name>
<range><lt>3.0.13,1</lt></range>
</package>
<package>
<name>openssl-quictls</name>
<range><lt>3.0.13</lt></range>
</package>
<package>
<name>openssl31</name>
<range><lt>3.1.5</lt></range>
</package>
<package>
<name>openssl31-quictls</name>
<range><lt>3.1.5</lt></range>
</package>
<package>
<name>openssl32</name>
<range><lt>3.2.1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The OpenSSL project reports:</p>
<blockquote cite="https://www.openssl.org/news/secadv/20240125.txt">
<p>Excessive time spent checking invalid RSA public keys (CVE-2023-6237)</p>
<p>PKCS12 Decoding crashes (CVE-2024-0727)</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2024-0727</cvename>
<cvename>CVE-2023-6237</cvename>
<url>https://www.openssl.org/news/secadv/20240125.txt</url>
<url>https://www.openssl.org/news/secadv/20240115.txt</url>
<url>https://www.openssl.org/news/openssl-3.0-notes.html</url>
<url>https://www.openssl.org/news/openssl-3.1-notes.html</url>
<url>https://www.openssl.org/news/openssl-3.2-notes.html</url>
</references>
<dates>
<discovery>2024-01-30</discovery>
<entry>2024-01-31</entry>
</dates>
</vuln>
<vuln vid="67c2eb06-5579-4595-801b-30355be24654">
<topic>lizard -- Negative size passed to memcpy resulting in memory corruption</topic>
<affects>
<package>
<name>lizard</name>
<range><lt>1.0_1</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>cve@mitre.org reports:</p>
<blockquote cite="https://github.com/inikep/lizard/issues/16">
<p>In Lizard v1.0 and LZ5 v2.0 (the prior release, before the product
was renamed), there is an unchecked buffer size during a memcpy in
the Lizard_decompress_LIZv1 function (lib/lizard_decompress_liz.h).
Remote attackers can leverage this vulnerability to cause a denial
of service via a crafted input file, as well as achieve remote code
execution.</p>
</blockquote>
</body>
</description>
<references>
<cvename>CVE-2018-11498</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2018-11498</url>