Gaati Track version 1.0-2023 suffers from an ignored default credential vulnerability.

**Goati Track 1.0-2023 Insecure Settings**

Posted Aug 12, 2024

Authored by indoushka

Gaati Track version 1.0-2023 suffers from an ignored default credential vulnerability.

tags | exploit

SHA-256 | a66751e0a18c1729e99f89ffd55d400c761bad76139bca2c36b5ffb404b06d8e

Download | Favorite | View

**Goati Track 1.0-2023 Insecure Settings**

    =============================================================================================================================================| # Title     : Gaati track v1.0-2023 Insecure Settings Vulnerability                                                                       || # Author    : indoushka                                                                                                                   || # Tested on : windows 10 Fr(Pro) / browser : Mozilla firefox 125.0.1 (64 bits)                                                            || # Vendor    : https://www.mayurik.com/source-code/P0998/best-courier-management-system-project-in-php                                     |=============================================================================================================================================poc :[+] Dorking İn Google Or Other Search Enggine.[+] Insecure Settings : appears to leave a default administrative account in place post installation.[+] use payload : user =  mayuri@admin.com & pass = admin[+] https://www/127.0.0.1/165.232.176.122/index.php?page=homeGreetings to :==================================================jericho * Larry W. Cashdollar * LiquidWorm * Hussin-X * D4NB4R |================================================================

**File Tags**

*   ActiveX (933)
*   Advisory (86,349)
*   Arbitrary (16,870)
*   BBS (2,859)
*   Bypass (1,861)
*   CGI (1,033)
*   Code Execution (7,810)
*   Conference (691)
*   Cracker (844)
*   CSRF (3,390)
*   DoS (25,071)
*   Encryption (2,389)
*   Exploit (53,180)
*   File Inclusion (4,262)
*   File Upload (994)
*   Firewall (822)
*   Info Disclosure (2,890)
*   Intrusion Detection (915)
*   Java (3,144)
*   JavaScript (896)
*   Kernel (7,202)
*   Local (14,795)
*   Magazine (586)
*   Overflow (13,169)
*   Perl (1,435)
*   PHP (5,225)
*   Proof of Concept (2,393)
*   Protocol (3,724)
*   Python (1,640)
*   Remote (31,655)
*   Root (3,635)
*   Rootkit (527)
*   Ruby (632)
*   Scanner (1,657)
*   Security Tool (8,027)
*   Shell (3,273)
*   Shellcode (1,217)
*   Sniffer (902)
*   Spoof (2,276)
*   SQL Injection (16,609)
*   TCP (2,441)
*   Trojan (690)
*   UDP (904)
*   Virus (669)
*   Vulnerability (32,967)
*   Web (9,963)
*   Whitepaper (3,782)
*   x86 (967)
*   XSS (18,250)
*   Other

**File Archives**

*   August 2024
*   July 2024
*   June 2024
*   May 2024
*   April 2024
*   March 2024
*   February 2024
*   January 2024
*   December 2023
*   November 2023
*   October 2023
*   September 2023
*   Older

**Systems**

*   AIX (429)
*   Apple (2,099)
*   BSD (377)
*   CentOS (58)
*   Cisco (1,927)
*   Debian (7,096)
*   Fedora (1,693)
*   FreeBSD (1,246)
*   Gentoo (4,567)
*   HPUX (880)
*   iOS (378)
*   iPhone (108)
*   IRIX (220)
*   Juniper (69)
*   Linux (50,707)
*   Mac OS X (691)
*   Mandriva (3,105)
*   NetBSD (256)
*   OpenBSD (489)
*   RedHat (16,485)
*   Slackware (941)
*   Solaris (1,611)
*   SUSE (1,444)
*   Ubuntu (9,737)
*   UNIX (9,435)
*   UnixWare (187)
*   Windows (6,672)
*   Other

Goati Track 1.0-2023 Insecure Settings

Gentoo Linux Security Advisory 202408-21 - Multiple vulnerabilities have been discovered in GPAC, the worst of which could lead to arbitrary code execution. Versions greater than or equal to 2.2.0 are affected.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Gentoo Linux Security Advisory                           GLSA 202408-21  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
                                           https://security.gentoo.org/  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal  
    Title: GPAC: Multiple Vulnerabilities  
     Date: August 10, 2024  
     Bugs: #785649, #835341  
       ID: 202408-21

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis  
========

Multiple vulnerabilities have been discovered in GPAC, the worst of  
which could lead to arbitrary code execution.

Background  
==========

GPAC is an implementation of the MPEG-4 Systems standard developed from  
scratch in ANSI C.

Affected packages  
=================

Package           Vulnerable    Unaffected  
----------------  ------------  ------------  
media-video/gpac  < 2.2.0       >= 2.2.0

Description  
===========

Multiple vulnerabilities have been discovered in GPAC. Please review the  
CVE identifiers referenced below for details.

Impact  
======

Please review the referenced CVE identifiers for details.

Workaround  
==========

There is no known workaround at this time.

Resolution  
==========

All GPAC users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=media-video/gpac-2.2.0"

References  
==========

[ 1 ] CVE-2020-22673  
      https://nvd.nist.gov/vuln/detail/CVE-2020-22673  
[ 2 ] CVE-2020-22674  
      https://nvd.nist.gov/vuln/detail/CVE-2020-22674  
[ 3 ] CVE-2020-22675  
      https://nvd.nist.gov/vuln/detail/CVE-2020-22675  
[ 4 ] CVE-2020-22677  
      https://nvd.nist.gov/vuln/detail/CVE-2020-22677  
[ 5 ] CVE-2020-22678  
      https://nvd.nist.gov/vuln/detail/CVE-2020-22678  
[ 6 ] CVE-2020-22679  
      https://nvd.nist.gov/vuln/detail/CVE-2020-22679  
[ 7 ] CVE-2020-25427  
      https://nvd.nist.gov/vuln/detail/CVE-2020-25427  
[ 8 ] CVE-2020-35979  
      https://nvd.nist.gov/vuln/detail/CVE-2020-35979  
[ 9 ] CVE-2020-35980  
      https://nvd.nist.gov/vuln/detail/CVE-2020-35980  
[ 10 ] CVE-2020-35981  
      https://nvd.nist.gov/vuln/detail/CVE-2020-35981  
[ 11 ] CVE-2020-35982  
      https://nvd.nist.gov/vuln/detail/CVE-2020-35982  
[ 12 ] CVE-2021-4043  
      https://nvd.nist.gov/vuln/detail/CVE-2021-4043  
[ 13 ] CVE-2021-21834  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21834  
[ 14 ] CVE-2021-21835  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21835  
[ 15 ] CVE-2021-21836  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21836  
[ 16 ] CVE-2021-21837  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21837  
[ 17 ] CVE-2021-21838  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21838  
[ 18 ] CVE-2021-21839  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21839  
[ 19 ] CVE-2021-21840  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21840  
[ 20 ] CVE-2021-21841  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21841  
[ 21 ] CVE-2021-21842  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21842  
[ 22 ] CVE-2021-21843  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21843  
[ 23 ] CVE-2021-21844  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21844  
[ 24 ] CVE-2021-21845  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21845  
[ 25 ] CVE-2021-21846  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21846  
[ 26 ] CVE-2021-21847  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21847  
[ 27 ] CVE-2021-21848  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21848  
[ 28 ] CVE-2021-21849  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21849  
[ 29 ] CVE-2021-21850  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21850  
[ 30 ] CVE-2021-21851  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21851  
[ 31 ] CVE-2021-21852  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21852  
[ 32 ] CVE-2021-21853  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21853  
[ 33 ] CVE-2021-21854  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21854  
[ 34 ] CVE-2021-21855  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21855  
[ 35 ] CVE-2021-21856  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21856  
[ 36 ] CVE-2021-21857  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21857  
[ 37 ] CVE-2021-21858  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21858  
[ 38 ] CVE-2021-21859  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21859  
[ 39 ] CVE-2021-21860  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21860  
[ 40 ] CVE-2021-21861  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21861  
[ 41 ] CVE-2021-21862  
      https://nvd.nist.gov/vuln/detail/CVE-2021-21862  
[ 42 ] CVE-2021-30014  
      https://nvd.nist.gov/vuln/detail/CVE-2021-30014  
[ 43 ] CVE-2021-30015  
      https://nvd.nist.gov/vuln/detail/CVE-2021-30015  
[ 44 ] CVE-2021-30019  
      https://nvd.nist.gov/vuln/detail/CVE-2021-30019  
[ 45 ] CVE-2021-30020  
      https://nvd.nist.gov/vuln/detail/CVE-2021-30020  
[ 46 ] CVE-2021-30022  
      https://nvd.nist.gov/vuln/detail/CVE-2021-30022  
[ 47 ] CVE-2021-30199  
      https://nvd.nist.gov/vuln/detail/CVE-2021-30199  
[ 48 ] CVE-2021-31254  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31254  
[ 49 ] CVE-2021-31255  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31255  
[ 50 ] CVE-2021-31256  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31256  
[ 51 ] CVE-2021-31257  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31257  
[ 52 ] CVE-2021-31258  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31258  
[ 53 ] CVE-2021-31259  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31259  
[ 54 ] CVE-2021-31260  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31260  
[ 55 ] CVE-2021-31261  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31261  
[ 56 ] CVE-2021-31262  
      https://nvd.nist.gov/vuln/detail/CVE-2021-31262  
[ 57 ] CVE-2021-32132  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32132  
[ 58 ] CVE-2021-32134  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32134  
[ 59 ] CVE-2021-32135  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32135  
[ 60 ] CVE-2021-32136  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32136  
[ 61 ] CVE-2021-32137  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32137  
[ 62 ] CVE-2021-32138  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32138  
[ 63 ] CVE-2021-32139  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32139  
[ 64 ] CVE-2021-32437  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32437  
[ 65 ] CVE-2021-32438  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32438  
[ 66 ] CVE-2021-32439  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32439  
[ 67 ] CVE-2021-32440  
      https://nvd.nist.gov/vuln/detail/CVE-2021-32440  
[ 68 ] CVE-2021-33361  
      https://nvd.nist.gov/vuln/detail/CVE-2021-33361  
[ 69 ] CVE-2021-33362  
      https://nvd.nist.gov/vuln/detail/CVE-2021-33362  
[ 70 ] CVE-2021-33363  
      https://nvd.nist.gov/vuln/detail/CVE-2021-33363  
[ 71 ] CVE-2021-33364  
      https://nvd.nist.gov/vuln/detail/CVE-2021-33364  
[ 72 ] CVE-2021-33365  
      https://nvd.nist.gov/vuln/detail/CVE-2021-33365  
[ 73 ] CVE-2021-33366  
      https://nvd.nist.gov/vuln/detail/CVE-2021-33366  
[ 74 ] CVE-2021-36412  
      https://nvd.nist.gov/vuln/detail/CVE-2021-36412  
[ 75 ] CVE-2021-36414  
      https://nvd.nist.gov/vuln/detail/CVE-2021-36414  
[ 76 ] CVE-2021-36417  
      https://nvd.nist.gov/vuln/detail/CVE-2021-36417  
[ 77 ] CVE-2021-36584  
      https://nvd.nist.gov/vuln/detail/CVE-2021-36584  
[ 78 ] CVE-2021-40559  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40559  
[ 79 ] CVE-2021-40562  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40562  
[ 80 ] CVE-2021-40563  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40563  
[ 81 ] CVE-2021-40564  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40564  
[ 82 ] CVE-2021-40565  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40565  
[ 83 ] CVE-2021-40566  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40566  
[ 84 ] CVE-2021-40567  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40567  
[ 85 ] CVE-2021-40568  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40568  
[ 86 ] CVE-2021-40569  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40569  
[ 87 ] CVE-2021-40570  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40570  
[ 88 ] CVE-2021-40571  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40571  
[ 89 ] CVE-2021-40572  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40572  
[ 90 ] CVE-2021-40573  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40573  
[ 91 ] CVE-2021-40574  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40574  
[ 92 ] CVE-2021-40575  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40575  
[ 93 ] CVE-2021-40576  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40576  
[ 94 ] CVE-2021-40592  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40592  
[ 95 ] CVE-2021-40606  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40606  
[ 96 ] CVE-2021-40607  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40607  
[ 97 ] CVE-2021-40608  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40608  
[ 98 ] CVE-2021-40609  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40609  
[ 99 ] CVE-2021-40942  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40942  
[ 100 ] CVE-2021-40944  
      https://nvd.nist.gov/vuln/detail/CVE-2021-40944  
[ 101 ] CVE-2021-41456  
      https://nvd.nist.gov/vuln/detail/CVE-2021-41456  
[ 102 ] CVE-2021-41457  
      https://nvd.nist.gov/vuln/detail/CVE-2021-41457  
[ 103 ] CVE-2021-41458  
      https://nvd.nist.gov/vuln/detail/CVE-2021-41458  
[ 104 ] CVE-2021-41459  
      https://nvd.nist.gov/vuln/detail/CVE-2021-41459  
[ 105 ] CVE-2021-44918  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44918  
[ 106 ] CVE-2021-44919  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44919  
[ 107 ] CVE-2021-44920  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44920  
[ 108 ] CVE-2021-44921  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44921  
[ 109 ] CVE-2021-44922  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44922  
[ 110 ] CVE-2021-44923  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44923  
[ 111 ] CVE-2021-44924  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44924  
[ 112 ] CVE-2021-44925  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44925  
[ 113 ] CVE-2021-44926  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44926  
[ 114 ] CVE-2021-44927  
      https://nvd.nist.gov/vuln/detail/CVE-2021-44927  
[ 115 ] CVE-2021-45258  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45258  
[ 116 ] CVE-2021-45259  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45259  
[ 117 ] CVE-2021-45260  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45260  
[ 118 ] CVE-2021-45262  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45262  
[ 119 ] CVE-2021-45263  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45263  
[ 120 ] CVE-2021-45266  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45266  
[ 121 ] CVE-2021-45267  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45267  
[ 122 ] CVE-2021-45288  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45288  
[ 123 ] CVE-2021-45289  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45289  
[ 124 ] CVE-2021-45291  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45291  
[ 125 ] CVE-2021-45292  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45292  
[ 126 ] CVE-2021-45297  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45297  
[ 127 ] CVE-2021-45760  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45760  
[ 128 ] CVE-2021-45762  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45762  
[ 129 ] CVE-2021-45763  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45763  
[ 130 ] CVE-2021-45764  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45764  
[ 131 ] CVE-2021-45767  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45767  
[ 132 ] CVE-2021-45831  
      https://nvd.nist.gov/vuln/detail/CVE-2021-45831  
[ 133 ] CVE-2021-46038  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46038  
[ 134 ] CVE-2021-46039  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46039  
[ 135 ] CVE-2021-46040  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46040  
[ 136 ] CVE-2021-46041  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46041  
[ 137 ] CVE-2021-46042  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46042  
[ 138 ] CVE-2021-46043  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46043  
[ 139 ] CVE-2021-46044  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46044  
[ 140 ] CVE-2021-46045  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46045  
[ 141 ] CVE-2021-46046  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46046  
[ 142 ] CVE-2021-46047  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46047  
[ 143 ] CVE-2021-46049  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46049  
[ 144 ] CVE-2021-46051  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46051  
[ 145 ] CVE-2021-46234  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46234  
[ 146 ] CVE-2021-46236  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46236  
[ 147 ] CVE-2021-46237  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46237  
[ 148 ] CVE-2021-46238  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46238  
[ 149 ] CVE-2021-46239  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46239  
[ 150 ] CVE-2021-46240  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46240  
[ 151 ] CVE-2021-46311  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46311  
[ 152 ] CVE-2021-46313  
      https://nvd.nist.gov/vuln/detail/CVE-2021-46313  
[ 153 ] CVE-2022-1035  
      https://nvd.nist.gov/vuln/detail/CVE-2022-1035  
[ 154 ] CVE-2022-1172  
      https://nvd.nist.gov/vuln/detail/CVE-2022-1172  
[ 155 ] CVE-2022-1222  
      https://nvd.nist.gov/vuln/detail/CVE-2022-1222  
[ 156 ] CVE-2022-1441  
      https://nvd.nist.gov/vuln/detail/CVE-2022-1441  
[ 157 ] CVE-2022-1795  
      https://nvd.nist.gov/vuln/detail/CVE-2022-1795  
[ 158 ] CVE-2022-2453  
      https://nvd.nist.gov/vuln/detail/CVE-2022-2453  
[ 159 ] CVE-2022-2454  
      https://nvd.nist.gov/vuln/detail/CVE-2022-2454  
[ 160 ] CVE-2022-2549  
      https://nvd.nist.gov/vuln/detail/CVE-2022-2549  
[ 161 ] CVE-2022-3178  
      https://nvd.nist.gov/vuln/detail/CVE-2022-3178  
[ 162 ] CVE-2022-3222  
      https://nvd.nist.gov/vuln/detail/CVE-2022-3222  
[ 163 ] CVE-2022-3957  
      https://nvd.nist.gov/vuln/detail/CVE-2022-3957  
[ 164 ] CVE-2022-4202  
      https://nvd.nist.gov/vuln/detail/CVE-2022-4202  
[ 165 ] CVE-2022-24249  
      https://nvd.nist.gov/vuln/detail/CVE-2022-24249  
[ 166 ] CVE-2022-24574  
      https://nvd.nist.gov/vuln/detail/CVE-2022-24574  
[ 167 ] CVE-2022-24575  
      https://nvd.nist.gov/vuln/detail/CVE-2022-24575  
[ 168 ] CVE-2022-24576  
      https://nvd.nist.gov/vuln/detail/CVE-2022-24576  
[ 169 ] CVE-2022-24577  
      https://nvd.nist.gov/vuln/detail/CVE-2022-24577  
[ 170 ] CVE-2022-24578  
      https://nvd.nist.gov/vuln/detail/CVE-2022-24578  
[ 171 ] CVE-2022-26967  
      https://nvd.nist.gov/vuln/detail/CVE-2022-26967  
[ 172 ] CVE-2022-27145  
      https://nvd.nist.gov/vuln/detail/CVE-2022-27145  
[ 173 ] CVE-2022-27146  
      https://nvd.nist.gov/vuln/detail/CVE-2022-27146  
[ 174 ] CVE-2022-27147  
      https://nvd.nist.gov/vuln/detail/CVE-2022-27147  
[ 175 ] CVE-2022-27148  
      https://nvd.nist.gov/vuln/detail/CVE-2022-27148  
[ 176 ] CVE-2022-29339  
      https://nvd.nist.gov/vuln/detail/CVE-2022-29339  
[ 177 ] CVE-2022-29340  
      https://nvd.nist.gov/vuln/detail/CVE-2022-29340  
[ 178 ] CVE-2022-29537  
      https://nvd.nist.gov/vuln/detail/CVE-2022-29537  
[ 179 ] CVE-2022-30976  
      https://nvd.nist.gov/vuln/detail/CVE-2022-30976  
[ 180 ] CVE-2022-36186  
      https://nvd.nist.gov/vuln/detail/CVE-2022-36186  
[ 181 ] CVE-2022-36190  
      https://nvd.nist.gov/vuln/detail/CVE-2022-36190  
[ 182 ] CVE-2022-36191  
      https://nvd.nist.gov/vuln/detail/CVE-2022-36191  
[ 183 ] CVE-2022-38530  
      https://nvd.nist.gov/vuln/detail/CVE-2022-38530  
[ 184 ] CVE-2022-43039  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43039  
[ 185 ] CVE-2022-43040  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43040  
[ 186 ] CVE-2022-43042  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43042  
[ 187 ] CVE-2022-43043  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43043  
[ 188 ] CVE-2022-43044  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43044  
[ 189 ] CVE-2022-43045  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43045  
[ 190 ] CVE-2022-43254  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43254  
[ 191 ] CVE-2022-43255  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43255  
[ 192 ] CVE-2022-45202  
      https://nvd.nist.gov/vuln/detail/CVE-2022-45202  
[ 193 ] CVE-2022-45204  
      https://nvd.nist.gov/vuln/detail/CVE-2022-45204  
[ 194 ] CVE-2022-45283  
      https://nvd.nist.gov/vuln/detail/CVE-2022-45283  
[ 195 ] CVE-2022-45343  
      https://nvd.nist.gov/vuln/detail/CVE-2022-45343  
[ 196 ] CVE-2022-46489  
      https://nvd.nist.gov/vuln/detail/CVE-2022-46489  
[ 197 ] CVE-2022-46490  
      https://nvd.nist.gov/vuln/detail/CVE-2022-46490  
[ 198 ] CVE-2022-47086  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47086  
[ 199 ] CVE-2022-47087  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47087  
[ 200 ] CVE-2022-47088  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47088  
[ 201 ] CVE-2022-47089  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47089  
[ 202 ] CVE-2022-47091  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47091  
[ 203 ] CVE-2022-47092  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47092  
[ 204 ] CVE-2022-47093  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47093  
[ 205 ] CVE-2022-47094  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47094  
[ 206 ] CVE-2022-47095  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47095  
[ 207 ] CVE-2022-47653  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47653  
[ 208 ] CVE-2022-47654  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47654  
[ 209 ] CVE-2022-47656  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47656  
[ 210 ] CVE-2022-47657  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47657  
[ 211 ] CVE-2022-47658  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47658  
[ 212 ] CVE-2022-47659  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47659  
[ 213 ] CVE-2022-47660  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47660  
[ 214 ] CVE-2022-47661  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47661  
[ 215 ] CVE-2022-47662  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47662  
[ 216 ] CVE-2022-47663  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47663

Availability  
============

This GLSA and any updates to it are available for viewing at  
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202408-21

Concerns?  
=========

Security is a primary focus of Gentoo Linux and ensuring the  
confidentiality and security of our users' machines is of utmost  
importance to us. Any security concerns should be addressed to  
security@gentoo.org or alternatively, you may file a bug at  
https://bugs.gentoo.org.

License  
=======

Copyright 2024 Gentoo Foundation, Inc; referenced text  
belongs to its owner(s).

The contents of this document are licensed under the  
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

Gentoo Linux Security Advisory 202408-21

Red Hat Security Advisory 2024-5194-03 - An update for the container-tools:rhel8 module is now available for Red Hat Enterprise Linux 8.8 Extended Update Support. Issues addressed include deserialization and memory exhaustion vulnerabilities.

    The following advisory data is extracted from:https://access.redhat.com/security/data/csaf/v2/advisories/2024/rhsa-2024_5194.jsonRed Hat officially shut down their mailing list notifications October 10, 2023.  Due to this, Packet Storm has recreated the below data as a reference point to raise awareness.  It must be noted that due to an inability to easily track revision updates without crawling Red Hat's archive, these advisories are single notifications and we strongly suggest that you visit the Red Hat provided links to ensure you have the latest information available if the subject matter listed pertains to your environment.- Packet Storm Staff====================================================================Red Hat Security AdvisorySynopsis:           Important: container-tools:rhel8 security updateAdvisory ID:        RHSA-2024:5194-03Product:            Red Hat Enterprise LinuxAdvisory URL:       https://access.redhat.com/errata/RHSA-2024:5194Issue date:         2024-08-12Revision:           03CVE Names:          CVE-2024-6104====================================================================Summary: An update for the container-tools:rhel8 module is now available for Red Hat Enterprise Linux 8.8 Extended Update Support.Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.Description:The container-tools module contains tools for working with containers, notably podman, buildah, skopeo, and runc.Security Fix(es):* go-retryablehttp: url might write sensitive information to log file (CVE-2024-6104)* gorilla/schema: Potential memory exhaustion attack due to sparse slice deserialization (CVE-2024-37298)For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.Solution:https://access.redhat.com/articles/11258CVEs:CVE-2024-6104References:https://access.redhat.com/security/updates/classification/#importanthttps://bugzilla.redhat.com/show_bug.cgi?id=2294000https://bugzilla.redhat.com/show_bug.cgi?id=2295010

Red Hat Security Advisory 2024-5194-03

Farmacia Gama version 1.0 suffers from an insecure direct object reference vulnerability.

**Farmacia Gama 1.0 Insecure Direct Object Reference**

Posted Aug 12, 2024

Authored by indoushka

Farmacia Gama version 1.0 suffers from an insecure direct object reference vulnerability.

tags | exploit

SHA-256 | 03b0ac64f0e5daeb38f4901ddbe680af2e5d9a8749a1b826aadf371e13ec4f05

Download | Favorite | View

**Farmacia Gama 1.0 Insecure Direct Object Reference**

    =============================================================================================================================================| # Title     : Farmacia Gama v1.0 IDOR Vulnerability                                                                                       || # Author    : indoushka                                                                                                                   || # Tested on : windows 10 Fr(Pro) / browser : Mozilla firefox 125.0.1 (64 bits)                                                            || # Vendor    : https://download-media.code-projects.org/2020/04/Farmacia_IN_PHP_CSS_JavaScript_AND_MYSQL__FREE_DOWNLOAD.zip                |=============================================================================================================================================poc :[+] Dorking İn Google Or Other Search Enggine.[+] Insecure Direct Object Reference : allows users to access the administrative interface.[+] use payload : /main.php[+] http://127.0.0.1/farmacia-master/main.phpGreetings to :============================================================jericho * Larry W. Cashdollar * LiquidWorm * Hussin-X * D4NB4R * CraCkEr |==========================================================================

**File Tags**

*   ActiveX (933)
*   Advisory (86,349)
*   Arbitrary (16,870)
*   BBS (2,859)
*   Bypass (1,861)
*   CGI (1,033)
*   Code Execution (7,810)
*   Conference (691)
*   Cracker (844)
*   CSRF (3,390)
*   DoS (25,071)
*   Encryption (2,389)
*   Exploit (53,180)
*   File Inclusion (4,262)
*   File Upload (994)
*   Firewall (822)
*   Info Disclosure (2,890)
*   Intrusion Detection (915)
*   Java (3,144)
*   JavaScript (896)
*   Kernel (7,202)
*   Local (14,795)
*   Magazine (586)
*   Overflow (13,169)
*   Perl (1,435)
*   PHP (5,225)
*   Proof of Concept (2,393)
*   Protocol (3,724)
*   Python (1,640)
*   Remote (31,655)
*   Root (3,635)
*   Rootkit (527)
*   Ruby (632)
*   Scanner (1,657)
*   Security Tool (8,027)
*   Shell (3,273)
*   Shellcode (1,217)
*   Sniffer (902)
*   Spoof (2,276)
*   SQL Injection (16,609)
*   TCP (2,441)
*   Trojan (690)
*   UDP (904)
*   Virus (669)
*   Vulnerability (32,967)
*   Web (9,963)
*   Whitepaper (3,782)
*   x86 (967)
*   XSS (18,250)
*   Other

**File Archives**

*   August 2024
*   July 2024
*   June 2024
*   May 2024
*   April 2024
*   March 2024
*   February 2024
*   January 2024
*   December 2023
*   November 2023
*   October 2023
*   September 2023
*   Older

**Systems**

*   AIX (429)
*   Apple (2,099)
*   BSD (377)
*   CentOS (58)
*   Cisco (1,927)
*   Debian (7,096)
*   Fedora (1,693)
*   FreeBSD (1,246)
*   Gentoo (4,567)
*   HPUX (880)
*   iOS (378)
*   iPhone (108)
*   IRIX (220)
*   Juniper (69)
*   Linux (50,707)
*   Mac OS X (691)
*   Mandriva (3,105)
*   NetBSD (256)
*   OpenBSD (489)
*   RedHat (16,485)
*   Slackware (941)
*   Solaris (1,611)
*   SUSE (1,444)
*   Ubuntu (9,737)
*   UNIX (9,435)
*   UnixWare (187)
*   Windows (6,672)
*   Other

Farmacia Gama 1.0 Insecure Direct Object Reference

Employee Management System version 1.0 suffers from an ignored default credential vulnerability.

**Employee Management System 1.0 Insecure Settings**

Posted Aug 12, 2024

Authored by indoushka

Employee Management System version 1.0 suffers from an ignored default credential vulnerability.

tags | exploit

SHA-256 | 4c729820d6c74d0d245f5de6b7ade8e4cebaa60f462a3e7bd0e326402db59bf4

Download | Favorite | View

**Employee Management System 1.0 Insecure Settings**

    =============================================================================================================================================| # Title     : Employee Management System v1.0 Insecure Settings Vulnerability                                                             || # Author    : indoushka                                                                                                                   || # Tested on : windows 10 Fr(Pro) / browser : Mozilla firefox 125.0.1 (64 bits)                                                            || # Vendor    : https://www.sourcecodester.com/php/16999/employee-management-system.html                                                    |=============================================================================================================================================poc :[+] Dorking İn Google Or Other Search Enggine.[+] Insecure Settings : appears to leave a default administrative account in place post installation.[+] use payload : user =  admin & pass = admin123[+] https://www/127.0.0.1/yorubanwitness000webhostappcom/admin/Greetings to :==================================================jericho * Larry W. Cashdollar * LiquidWorm * Hussin-X * D4NB4R |================================================================

**File Tags**

*   ActiveX (933)
*   Advisory (86,349)
*   Arbitrary (16,870)
*   BBS (2,859)
*   Bypass (1,861)
*   CGI (1,033)
*   Code Execution (7,810)
*   Conference (691)
*   Cracker (844)
*   CSRF (3,390)
*   DoS (25,071)
*   Encryption (2,389)
*   Exploit (53,180)
*   File Inclusion (4,262)
*   File Upload (994)
*   Firewall (822)
*   Info Disclosure (2,890)
*   Intrusion Detection (915)
*   Java (3,144)
*   JavaScript (896)
*   Kernel (7,202)
*   Local (14,795)
*   Magazine (586)
*   Overflow (13,169)
*   Perl (1,435)
*   PHP (5,225)
*   Proof of Concept (2,393)
*   Protocol (3,724)
*   Python (1,640)
*   Remote (31,655)
*   Root (3,635)
*   Rootkit (527)
*   Ruby (632)
*   Scanner (1,657)
*   Security Tool (8,027)
*   Shell (3,273)
*   Shellcode (1,217)
*   Sniffer (902)
*   Spoof (2,276)
*   SQL Injection (16,609)
*   TCP (2,441)
*   Trojan (690)
*   UDP (904)
*   Virus (669)
*   Vulnerability (32,967)
*   Web (9,963)
*   Whitepaper (3,782)
*   x86 (967)
*   XSS (18,250)
*   Other

**File Archives**

*   August 2024
*   July 2024
*   June 2024
*   May 2024
*   April 2024
*   March 2024
*   February 2024
*   January 2024
*   December 2023
*   November 2023
*   October 2023
*   September 2023
*   Older

**Systems**

*   AIX (429)
*   Apple (2,099)
*   BSD (377)
*   CentOS (58)
*   Cisco (1,927)
*   Debian (7,096)
*   Fedora (1,693)
*   FreeBSD (1,246)
*   Gentoo (4,567)
*   HPUX (880)
*   iOS (378)
*   iPhone (108)
*   IRIX (220)
*   Juniper (69)
*   Linux (50,707)
*   Mac OS X (691)
*   Mandriva (3,105)
*   NetBSD (256)
*   OpenBSD (489)
*   RedHat (16,485)
*   Slackware (941)
*   Solaris (1,611)
*   SUSE (1,444)
*   Ubuntu (9,737)
*   UNIX (9,435)
*   UnixWare (187)
*   Windows (6,672)
*   Other

Employee Management System 1.0 Insecure Settings

Red Hat Security Advisory 2024-5193-03 - An update for the httpd:2.4 module is now available for Red Hat Enterprise Linux 8.

    The following advisory data is extracted from:https://access.redhat.com/security/data/csaf/v2/advisories/2024/rhsa-2024_5193.jsonRed Hat officially shut down their mailing list notifications October 10, 2023.  Due to this, Packet Storm has recreated the below data as a reference point to raise awareness.  It must be noted that due to an inability to easily track revision updates without crawling Red Hat's archive, these advisories are single notifications and we strongly suggest that you visit the Red Hat provided links to ensure you have the latest information available if the subject matter listed pertains to your environment.- Packet Storm Staff====================================================================Red Hat Security AdvisorySynopsis:           Important: httpd:2.4 security updateAdvisory ID:        RHSA-2024:5193-03Product:            Red Hat Enterprise LinuxAdvisory URL:       https://access.redhat.com/errata/RHSA-2024:5193Issue date:         2024-08-12Revision:           03CVE Names:          CVE-2024-38476====================================================================Summary: An update for the httpd:2.4 module is now available for Red Hat Enterprise Linux 8.Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.Description:The httpd packages provide the Apache HTTP Server, a powerful, efficient, and extensible web server.Security Fix(es):* httpd: Security issues via?backend applications whose response headers are malicious or exploitable (CVE-2024-38476)For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.Solution:https://access.redhat.com/articles/11258CVEs:CVE-2024-38476References:https://access.redhat.com/security/updates/classification/#importanthttps://bugzilla.redhat.com/show_bug.cgi?id=2295015

Red Hat Security Advisory 2024-5193-03

Gentoo Linux Security Advisory 202408-20 - Multiple vulnerabilities have been discovered in libde265, the worst of which could lead to arbitrary code execution. Versions greater than or equal to 1.0.11 are affected.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Gentoo Linux Security Advisory                           GLSA 202408-20  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
                                           https://security.gentoo.org/  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal  
    Title: libde265: Multiple Vulnerabilities  
     Date: August 10, 2024  
     Bugs: #813486, #889876  
       ID: 202408-20

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis  
========

Multiple vulnerabilities have been discovered in libde265, the worst of  
which could lead to arbitrary code execution.

Background  
==========

Open h.265 video codec implementation.

Affected packages  
=================

Package              Vulnerable    Unaffected  
-------------------  ------------  ------------  
media-libs/libde265  < 1.0.11      >= 1.0.11

Description  
===========

Multiple vulnerabilities have been discovered in libde265. Please review  
the CVE identifiers referenced below for details.

Impact  
======

Please review the referenced CVE identifiers for details.

Workaround  
==========

There is no known workaround at this time.

Resolution  
==========

All libde265 users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=media-libs/libde265-1.0.11"

References  
==========

[ 1 ] CVE-2020-21594  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21594  
[ 2 ] CVE-2020-21595  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21595  
[ 3 ] CVE-2020-21596  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21596  
[ 4 ] CVE-2020-21597  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21597  
[ 5 ] CVE-2020-21598  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21598  
[ 6 ] CVE-2020-21599  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21599  
[ 7 ] CVE-2020-21600  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21600  
[ 8 ] CVE-2020-21601  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21601  
[ 9 ] CVE-2020-21602  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21602  
[ 10 ] CVE-2020-21603  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21603  
[ 11 ] CVE-2020-21604  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21604  
[ 12 ] CVE-2020-21605  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21605  
[ 13 ] CVE-2020-21606  
      https://nvd.nist.gov/vuln/detail/CVE-2020-21606  
[ 14 ] CVE-2021-35452  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35452  
[ 15 ] CVE-2021-36408  
      https://nvd.nist.gov/vuln/detail/CVE-2021-36408  
[ 16 ] CVE-2021-36409  
      https://nvd.nist.gov/vuln/detail/CVE-2021-36409  
[ 17 ] CVE-2021-36410  
      https://nvd.nist.gov/vuln/detail/CVE-2021-36410  
[ 18 ] CVE-2021-36411  
      https://nvd.nist.gov/vuln/detail/CVE-2021-36411  
[ 19 ] CVE-2022-1253  
      https://nvd.nist.gov/vuln/detail/CVE-2022-1253  
[ 20 ] CVE-2022-43235  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43235  
[ 21 ] CVE-2022-43236  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43236  
[ 22 ] CVE-2022-43237  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43237  
[ 23 ] CVE-2022-43238  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43238  
[ 24 ] CVE-2022-43239  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43239  
[ 25 ] CVE-2022-43240  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43240  
[ 26 ] CVE-2022-43241  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43241  
[ 27 ] CVE-2022-43242  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43242  
[ 28 ] CVE-2022-43243  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43243  
[ 29 ] CVE-2022-43244  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43244  
[ 30 ] CVE-2022-43245  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43245  
[ 31 ] CVE-2022-43248  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43248  
[ 32 ] CVE-2022-43249  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43249  
[ 33 ] CVE-2022-43250  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43250  
[ 34 ] CVE-2022-43252  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43252  
[ 35 ] CVE-2022-43253  
      https://nvd.nist.gov/vuln/detail/CVE-2022-43253  
[ 36 ] CVE-2022-47655  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47655  
[ 37 ] CVE-2022-47664  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47664  
[ 38 ] CVE-2022-47665  
      https://nvd.nist.gov/vuln/detail/CVE-2022-47665  
[ 39 ] CVE-2023-24751  
      https://nvd.nist.gov/vuln/detail/CVE-2023-24751  
[ 40 ] CVE-2023-24752  
      https://nvd.nist.gov/vuln/detail/CVE-2023-24752  
[ 41 ] CVE-2023-24754  
      https://nvd.nist.gov/vuln/detail/CVE-2023-24754  
[ 42 ] CVE-2023-24755  
      https://nvd.nist.gov/vuln/detail/CVE-2023-24755  
[ 43 ] CVE-2023-24756  
      https://nvd.nist.gov/vuln/detail/CVE-2023-24756  
[ 44 ] CVE-2023-24757  
      https://nvd.nist.gov/vuln/detail/CVE-2023-24757  
[ 45 ] CVE-2023-24758  
      https://nvd.nist.gov/vuln/detail/CVE-2023-24758  
[ 46 ] CVE-2023-25221  
      https://nvd.nist.gov/vuln/detail/CVE-2023-25221

Availability  
============

This GLSA and any updates to it are available for viewing at  
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202408-20

Concerns?  
=========

Security is a primary focus of Gentoo Linux and ensuring the  
confidentiality and security of our users' machines is of utmost  
importance to us. Any security concerns should be addressed to  
security@gentoo.org or alternatively, you may file a bug at  
https://bugs.gentoo.org.

License  
=======

Copyright 2024 Gentoo Foundation, Inc; referenced text  
belongs to its owner(s).

The contents of this document are licensed under the  
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

Gentoo Linux Security Advisory 202408-20

Quay.io is Red Hat’s hosted container registry service that serves enterprise users,  open source community projects, and Red Hat customers worldwide. One of the most used features of Quay.io, besides storing and serving container images, is the comprehensive security vulnerability reporting for any uploaded image. Because Red Hat is committed to making open source software more accessible, this functionality is also available on the free tier, provided by the Clair static vulnerability analyzer project.Clair allows users to analyze millions of container images and billions of layers, and pr

Quay.io is Red Hat’s hosted container registry service that serves enterprise users,  open source community projects, and Red Hat customers worldwide. One of the most used features of Quay.io, besides storing and serving container images, is the comprehensive security vulnerability reporting for any uploaded image. Because Red Hat is committed to making open source software more accessible, this functionality is also available on the free tier, provided by the Clair static vulnerability analyzer project.

Clair allows users to analyze millions of container images and billions of layers, and provides reports in real-time without manual resubmission. In the coming weeks, we're rolling out a significant update to the Clair backend service that changes the vulnerabilities for Red Hat content reported on Quay.io.

**Introduction of CSAF/VEX**

Red Hat content includes all container images that either use Red Hat Enterprise Linux (RHEL) or the Universal Base Image (UBI) as the base images, and contain Red Hat components as RPM packages or non-RPM artifacts. The Red Hat Product Security team releases vulnerability data specifically for this content. This data in turn, is consumed by the Clair instance behind Quay.io, which produces the vulnerability reports for container images.

Previously, those kinds of reports were published in the OVAL v2 format. The OVAL v2 format will remain available, but it won't receive new features, and upcoming products like RHEL 10 won't have OVAL v2 feeds.

The vulnerability reports for Red Hat content on Quay.io is changing with the introduction of CSAF/VEX vulnerability data in Clair. The Common Security Advisory Framework (CSAF) is a standardized security advisory format that Red Hat is switching to in order to communicate vulnerabilities affecting Red Hat products.

In particular, the Vulnerability Exploitability Exchange (VEX) profile in CSAF format is now used to describe (with greater detail than before) which Red Hat products and which components are impacted (or known not to be impacted) by a specific vulnerability identified by the Common Vulnerability and Exposures ID (CVE).

The new format generally leads to more accuracy in vulnerability reports, which helps users cut through the noise generated by security vulnerabilities originating from base images or language package manager imports.

**Changes to vulnerability reports for Red Hat content**

With the introduction of CSAF/VEX support in Clair, vulnerability reports for Red Hat content on Quay.io become CVE-centric.

Previously, Red Hat image content vulnerability reports were focused on Red Hat Security Advisories (RHSA). These informed you when specific product components were vulnerable to a known CVE, and how to remediate the vulnerability. A RHSA could encompass multiple CVEs of different severity levels and products affected.

This approach made it difficult to report on the actual severity of a vulnerability, because one report could cover multiple packages (each with different severity levels). Also, when you searched for a specific CVE identifier, you had to look at the synopsis of each vulnerability reported in the Quay.io UI.

But with CSAF/VEX, each vulnerability is shown separately, with one CVE identifier on each line item. This makes it easier to understand which CVE is matched against a particular container image.

This means you'll see more vulnerabilities reported for a given container image than before, but that's good! Now you have precise information about vulnerabilities detected in a given container image. The reporting change will affect existing and new images pushed to Quay.io, so you get precise detail on all images.

**Unfixed vulnerabilities are now included by default**

As part of the format change of Red Hat product security data, unfixed vulnerabilities are shown by default for Red Hat product content discovered by Clair in a container image. These are vulnerabilities for which no security errata from Red Hat exist. This may happen when a patch is still in the works, or the development efforts of a patch are out of proportion with the exploitability of the vulnerability and combination with its severity rating.

Previously, Quay.io's Clair instance was configured to not report unfixed vulnerabilities due to historical concerns with the growth of vulnerability reports and system scalability. These concerns have been addressed, and Quay.io is now in line with the Red Hat Quay product, which ships Clair and is configured to report unfixed vulnerabilities by default.

In Quay.io, you can hide unfixed vulnerabilities from the report in the UI:

With these changes, Quay.io makes verifying whether a given vulnerability impacts a specific image easier. Many users search by CVE identifier (for instance, CVE-2024-6387). With CVE-centric reporting, the search function in the vulnerability report table reveals whether a given CVE impacts Red Hat container images.

Another improvement is the accuracy in severity grading. Each vulnerability reported by Red Hat comes with its own VEX file, and has a severity grade. The severity grade is then used to report the vulnerability inside Quay.io for the specific CVE matched against a particular package found by Clair. Security reports no longer aggregate severity ratings behind security advisories, but list each vulnerability identified individually, along with its own severity rating. Note that Clair harmonizes severity ratings across different vulnerability sources to aid with prioritization according to this mapping logic.

At first, this may seem like an increase in vulnerabilities for an existing image, but it actually reflects the enhanced precision of reporting. You can put this new information to good use by updating your runtime dependencies, and rebasing on a newer version of your base image to address vulnerabilities. If you host a base image, you can even use Quay.io's repository notifications on a newly pushed image tag to automate rebuilds of a new base image.

Improved vulnerability reporting on Quay.io

Six vulnerabilities in ATM-maker Diebold Nixdorf’s popular Vynamic Security Suite could have been exploited to control ATMs using “relatively simplistic attacks.”

There is a grand tradition at the annual Defcon security conference in Las Vegas of hacking ATMs. Unlocking them with safecracking techniques, rigging them to steal users' personal data and PINs, crafting and refining ATM malware and, of course, hacking them to spit out all their cash. Many of these projects targeted what are known as retail ATMs, freestanding devices like those you'd find at a gas station or a bar. But on Friday, independent researcher Matt Burch is presenting findings related to the “financial” or “enterprise” ATMs used in banks and other large institutions.

Burch is demonstrating six vulnerabilities in ATM-maker Diebold Nixdorf’s widely deployed security solution, known as Vynamic Security Suite (VSS). The vulnerabilities, which the company says have all been patched, could be exploited by attackers to bypass an unpatched ATM's hard drive encryption and take full control of the machine. And while there are fixes available for the bugs, Burch warns that, in practice, the patches may not be widely deployed, potentially leaving some ATMs and cash-out systems exposed.

“Vynamic Security Suite does a number of things—it has endpoint protection, USB filtering, delegated access, and much more,” Burch tells WIRED. “But the specific attack surface that I’m taking advantage of is the hard drive encryption module. And there are six vulnerabilities, because I would identify a path and files to exploit, and then I would report it to Diebold, they would patch that issue, and then I would find another way to achieve the same outcome. They’re relatively simplistic attacks.”

The vulnerabilities Burch found are all in VSS's functionality to turn on disk encryption for ATM hard drives. Burch says that most ATM manufacturers rely on Microsoft's BitLlocker Windows encryption for this purpose, but Diebold Nixdorf’s VSS uses a third-party integration to run an integrity check. The system is set up in a dual-boot configuration that has both Linux and Windows partitions. Before the operating system boots, the Linux partition runs a signature integrity check to validate that the ATM hasn't been compromised, and then boots it into Windows for normal operation.

“The problem is, in order to do all of that, they decrypt the system, which opens up the opportunity,” Burch says. “The core deficiency that I’m exploiting is that the Linux partition was not encrypted.”

Burch found that he could manipulate the location of critical system validation files to redirect code execution; in other words, grant himself control of the ATM.

Diebold Nixdorf spokesperson Michael Jacobsen tells WIRED that Burch first disclosed the findings to them in 2022 and that the company has been in touch with Burch about his Defcon talk. The company says that the vulnerabilities Burch is presenting were all addressed with patches in 2022. Burch notes, though, that as he went back to the company with new versions of the vulnerabilities over the past couple of years, his understanding is that the company continued to address some of the findings with patches in 2023. And Burch adds that he believes Diebold Nixdorf addressed the vulnerabilities on a more fundamental level in April with VSS version 4.4 that encrypts the Linux partition.

In spite of all of this, Burch says, it would probably still be possible to find a path to exploit similar vulnerabilities, but “it’s significantly harder now.” More importantly, though, he notes that it can involve significant infrastructure initiatives for large institutions to actually update enterprise ATMs and it's very possible that there are ATMs and cash-out systems that are still running old versions of VSS.

“We’re currently working to ensure our customers are up to date and using the current version appropriate for their environment,” Jacobsen tells WIRED. He added that Diebold Nixdorf's customers should not assume that implementing different disk encryption, like Microsoft BitLocker, would be feasible. “One of Matt’s recommendations for switching to an enterprise disk encryption product, especially Bitlocker, is vulnerable in our environments,” Jacobsen says. “A Bitlocker-encrypted machine can be compromised, and Microsoft will not address this, as the ATM use case is not in their scope.”

This may refer to ongoing, real-world attacks on ATM machines that use malware to steal cash from enterprise ATMs made by multiple manufacturers. These incidents illustrate that there are very real concerns about ATM vulnerabilities being exploited, even though most attacks require physically targeting ATMs and can't be carried out remotely.

“Doing the attack requires physical access where you open the top portion of the ATM, pull the hard drive out, and then patch the contents of the hard drive,” Burch says. “An unrehearsed execution would not be easy to do. But it's absolutely feasible if you know what you’re looking at. Similar attacks have been executed in under 10 minutes. Organized crime is presumably training people in how to do these attacks.”

As long as attackers are finding success and making money from ATM cash-out attacks, there will be Defcon talks about what the next frontiers of ATM hacking may look like.

ATM Software Flaws Left Piles of Cash for Anyone Who Knew to Look

Gentoo Linux Security Advisory 202408-19 - Multiple vulnerabilities have been discovered in ncurses, the worst of which could lead to a denial of service. Versions greater than or equal to 6.4_p20230408 are affected.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Gentoo Linux Security Advisory                           GLSA 202408-19  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
                                           https://security.gentoo.org/  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal  
    Title: ncurses: Multiple Vulnerabilities  
     Date: August 09, 2024  
     Bugs: #839351, #904247  
       ID: 202408-19

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis  
=======  
Multiple vulnerabilities have been discovered in ncurses, the worst of  
which could lead to a denial of service.

Background  
=========  
Free software emulation of curses in System V.

Affected packages  
================  
Package                  Vulnerable       Unaffected  
-----------------------  ---------------  ----------------  
sys-libs/ncurses         < 6.4_p20230408  >= 6.4_p20230408  
sys-libs/ncurses-compat  < 6.4_p20240330  >= 6.4_p20240330

Description  
==========  
Multiple vulnerabilities have been discovered in ncurses. Please review  
the CVE identifiers referenced below for details.

Impact  
=====  
Please review the referenced CVE identifiers for details.

Workaround  
=========  
There is no known workaround at this time.

Resolution  
=========  
All ncurses users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=sys-libs/ncurses-6.4_p20230408"  
  # emerge --ask --oneshot --verbose ">=sys-libs/ncurses-compat-6.4_p20240330"

References  
=========  
[ 1 ] CVE-2022-29458  
      https://nvd.nist.gov/vuln/detail/CVE-2022-29458  
[ 2 ] CVE-2023-29491  
      https://nvd.nist.gov/vuln/detail/CVE-2023-29491

Availability  
===========  
This GLSA and any updates to it are available for viewing at  
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202408-19

Concerns?  
========  
Security is a primary focus of Gentoo Linux and ensuring the  
confidentiality and security of our users' machines is of utmost  
importance to us. Any security concerns should be addressed to  
security@gentoo.org or alternatively, you may file a bug at  
https://bugs.gentoo.org.

License  
======  
Copyright 2024 Gentoo Foundation, Inc; referenced text  
belongs to its owner(s).

The contents of this document are licensed under the  
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

Tag

#linux