ALT-BU-2021-4170-1
Branch sisyphus update bulletin.
Closed vulnerabilities
BDU:2020-03979
Уязвимость веб-сервера Coturn, связанная с разыменованием нулевого указателя, позволяющая нарушителю вызвать отказ в обслуживании
BDU:2020-03980
Уязвимость веб-сервера Coturn, связанная с выходом операции за допустимые границы буфера данных, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании
BDU:2020-03981
Уязвимость буфера ответа STUN/TURN веб-сервера Coturn, позволяющая нарушителю получить доступ к конфиденциальным данным
BDU:2021-01906
Уязвимость веб-сервера Coturn, связанная с некорректной проверкой вводимых данных, позволяющая нарушителю получить доступ к конфиденциальным данным и нарушить их целостность
Modified: 2024-11-21
CVE-2020-26262
Coturn is free open source implementation of TURN and STUN Server. Coturn before version 4.5.2 by default does not allow peers to connect and relay packets to loopback addresses in the range of `127.x.x.x`. However, it was observed that when sending a `CONNECT` request with the `XOR-PEER-ADDRESS` value of `0.0.0.0`, a successful response was received and subsequently, `CONNECTIONBIND` also received a successful response. Coturn then is able to relay packets to the loopback interface. Additionally, when coturn is listening on IPv6, which is default, the loopback interface can also be reached by making use of either `[::1]` or `[::]` as the peer address. By using the address `0.0.0.0` as the peer address, a malicious user will be able to relay packets to the loopback interface, unless `--denied-peer-ip=0.0.0.0` (or similar) has been specified. Since the default configuration implies that loopback peers are not allowed, coturn administrators may choose to not set the `denied-peer-ip` setting. The issue patched in version 4.5.2. As a workaround the addresses in the address block `0.0.0.0/8`, `[::1]` and `[::]` should be denied by default unless `--allow-loopback-peers` has been specified.
- https://github.com/coturn/coturn/blob/57180ab60afcaeb13537e69ae8cb8aefd8f3f546/ChangeLog#L48
- https://github.com/coturn/coturn/blob/57180ab60afcaeb13537e69ae8cb8aefd8f3f546/ChangeLog#L48
- https://github.com/coturn/coturn/commit/abfe1fd08d78baa0947d17dac0f7411c3d948e4d
- https://github.com/coturn/coturn/commit/abfe1fd08d78baa0947d17dac0f7411c3d948e4d
- https://github.com/coturn/coturn/security/advisories/GHSA-6g6j-r9rf-cm7p
- https://github.com/coturn/coturn/security/advisories/GHSA-6g6j-r9rf-cm7p
- FEDORA-2021-dee141fc61
- FEDORA-2021-dee141fc61
- FEDORA-2021-32d0068851
- FEDORA-2021-32d0068851
Modified: 2024-11-21
CVE-2020-4067
In coturn before version 4.5.1.3, there is an issue whereby STUN/TURN response buffer is not initialized properly. There is a leak of information between different client connections. One client (an attacker) could use their connection to intelligently query coturn to get interesting bytes in the padding bytes from the connection of another client. This has been fixed in 4.5.1.3.
- openSUSE-SU-2020:0937
- openSUSE-SU-2020:0937
- https://github.com/coturn/coturn/blob/aab60340b201d55c007bcdc853230f47aa2dfdf1/ChangeLog#L15
- https://github.com/coturn/coturn/blob/aab60340b201d55c007bcdc853230f47aa2dfdf1/ChangeLog#L15
- https://github.com/coturn/coturn/issues/583
- https://github.com/coturn/coturn/issues/583
- https://github.com/coturn/coturn/security/advisories/GHSA-c8r8-8vp5-6gcm
- https://github.com/coturn/coturn/security/advisories/GHSA-c8r8-8vp5-6gcm
- [debian-lts-announce] 20200701 [SECURITY] [DLA 2271-1] coturn security update
- [debian-lts-announce] 20200701 [SECURITY] [DLA 2271-1] coturn security update
- FEDORA-2020-d946f64eea
- FEDORA-2020-d946f64eea
- FEDORA-2020-9eadf517de
- FEDORA-2020-9eadf517de
- USN-4415-1
- USN-4415-1
- DSA-4711
- DSA-4711
Modified: 2024-11-21
CVE-2020-6061
An exploitable heap out-of-bounds read vulnerability exists in the way CoTURN 4.5.1.1 web server parses POST requests. A specially crafted HTTP POST request can lead to information leaks and other misbehavior. An attacker needs to send an HTTPS request to trigger this vulnerability.
- FEDORA-2020-f3fcb1608a
- FEDORA-2020-f3fcb1608a
- FEDORA-2020-6efa0fc869
- FEDORA-2020-6efa0fc869
- FEDORA-2020-305c173af8
- FEDORA-2020-305c173af8
- https://talosintelligence.com/vulnerability_reports/TALOS-2020-0984
- https://talosintelligence.com/vulnerability_reports/TALOS-2020-0984
- USN-4415-1
- USN-4415-1
- DSA-4711
- DSA-4711
Modified: 2024-11-21
CVE-2020-6062
An exploitable denial-of-service vulnerability exists in the way CoTURN 4.5.1.1 web server parses POST requests. A specially crafted HTTP POST request can lead to server crash and denial of service. An attacker needs to send an HTTP request to trigger this vulnerability.
- FEDORA-2020-f3fcb1608a
- FEDORA-2020-f3fcb1608a
- FEDORA-2020-6efa0fc869
- FEDORA-2020-6efa0fc869
- FEDORA-2020-305c173af8
- FEDORA-2020-305c173af8
- https://talosintelligence.com/vulnerability_reports/TALOS-2020-0985
- https://talosintelligence.com/vulnerability_reports/TALOS-2020-0985
- USN-4415-1
- USN-4415-1
- DSA-4711
- DSA-4711
Closed vulnerabilities
BDU:2022-01073
Уязвимость библиотеки libssh, связанная с выходом операции за границы буфера в памяти, позволяющая нарушителю вызвать отказ в обслуживании
Modified: 2024-11-21
CVE-2021-3634
A flaw has been found in libssh in versions prior to 0.9.6. The SSH protocol keeps track of two shared secrets during the lifetime of the session. One of them is called secret_hash and the other session_id. Initially, both of them are the same, but after key re-exchange, previous session_id is kept and used as an input to new secret_hash. Historically, both of these buffers had shared length variable, which worked as long as these buffers were same. But the key re-exchange operation can also change the key exchange method, which can be based on hash of different size, eventually creating "secret_hash" of different size than the session_id has. This becomes an issue when the session_id memory is zeroed or when it is used again during second key re-exchange.
- https://bugzilla.redhat.com/show_bug.cgi?id=1978810
- https://bugzilla.redhat.com/show_bug.cgi?id=1978810
- FEDORA-2021-f2a020a065
- FEDORA-2021-f2a020a065
- FEDORA-2021-288925ac19
- FEDORA-2021-288925ac19
- FEDORA-2021-ec797b6a96
- FEDORA-2021-ec797b6a96
- GLSA-202312-05
- GLSA-202312-05
- https://security.netapp.com/advisory/ntap-20211004-0003/
- https://security.netapp.com/advisory/ntap-20211004-0003/
- DSA-4965
- DSA-4965
- https://www.oracle.com/security-alerts/cpujan2022.html
- https://www.oracle.com/security-alerts/cpujan2022.html
Package propagator updated to version 20210831-alt1 for branch sisyphus in task 284316.
Closed bugs
propagator: не работает автоматическая загрузка по сети при наличии >= 2 интерфейсов
Closed vulnerabilities
BDU:2019-04710
Уязвимость компонента main.c FTP-сервера ProFTPD, связанная с выполнением цикла с недоступным условием выхода, позволяющая нарушителю вызвать отказ в обслуживании
Modified: 2024-11-21
CVE-2017-7418
ProFTPD before 1.3.5e and 1.3.6 before 1.3.6rc5 controls whether the home directory of a user could contain a symbolic link through the AllowChrootSymlinks configuration option, but checks only the last path component when enforcing AllowChrootSymlinks. Attackers with local access could bypass the AllowChrootSymlinks control by replacing a path component (other than the last one) with a symbolic link. The threat model includes an attacker who is not granted full filesystem access by a hosting provider, but can reconfigure the home directory of an FTP user.
- http://bugs.proftpd.org/show_bug.cgi?id=4295
- http://bugs.proftpd.org/show_bug.cgi?id=4295
- openSUSE-SU-2019:1836
- openSUSE-SU-2019:1836
- openSUSE-SU-2019:1870
- openSUSE-SU-2019:1870
- openSUSE-SU-2020:0031
- openSUSE-SU-2020:0031
- 97409
- 97409
- https://github.com/proftpd/proftpd/commit/ecff21e0d0e84f35c299ef91d7fda088e516d4ed
- https://github.com/proftpd/proftpd/commit/ecff21e0d0e84f35c299ef91d7fda088e516d4ed
- https://github.com/proftpd/proftpd/commit/f59593e6ff730b832dbe8754916cb5c821db579f
- https://github.com/proftpd/proftpd/commit/f59593e6ff730b832dbe8754916cb5c821db579f
- https://github.com/proftpd/proftpd/pull/444/commits/349addc3be4fcdad9bd4ec01ad1ccd916c898ed8
- https://github.com/proftpd/proftpd/pull/444/commits/349addc3be4fcdad9bd4ec01ad1ccd916c898ed8
Modified: 2024-11-21
CVE-2019-18217
ProFTPD before 1.3.6b and 1.3.7rc before 1.3.7rc2 allows remote unauthenticated denial-of-service due to incorrect handling of overly long commands because main.c in a child process enters an infinite loop.
- openSUSE-SU-2020:0031
- openSUSE-SU-2020:0031
- https://cert-portal.siemens.com/productcert/pdf/ssa-940889.pdf
- https://cert-portal.siemens.com/productcert/pdf/ssa-940889.pdf
- https://github.com/proftpd/proftpd/blob/1.3.6/NEWS
- https://github.com/proftpd/proftpd/blob/1.3.6/NEWS
- https://github.com/proftpd/proftpd/blob/1.3.6/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/1.3.6/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/master/NEWS
- https://github.com/proftpd/proftpd/blob/master/NEWS
- https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
- https://github.com/proftpd/proftpd/issues/846
- https://github.com/proftpd/proftpd/issues/846
- [debian-lts-announce] 20191027 [SECURITY] [DLA 1974-1] proftpd-dfsg security update
- [debian-lts-announce] 20191027 [SECURITY] [DLA 1974-1] proftpd-dfsg security update
- FEDORA-2019-ae019c7e9f
- FEDORA-2019-ae019c7e9f
- FEDORA-2019-7559f29ace
- FEDORA-2019-7559f29ace
- FEDORA-2019-848e410cfb
- FEDORA-2019-848e410cfb
- 20191106 [SECURITY] [DSA 4559-1] proftpd-dfsg security update
- 20191106 [SECURITY] [DSA 4559-1] proftpd-dfsg security update
- GLSA-202003-35
- GLSA-202003-35
- DSA-4559
- DSA-4559
Modified: 2024-11-21
CVE-2019-19269
An issue was discovered in tls_verify_crl in ProFTPD through 1.3.6b. A dereference of a NULL pointer may occur. This pointer is returned by the OpenSSL sk_X509_REVOKED_value() function when encountering an empty CRL installed by a system administrator. The dereference occurs when validating the certificate of a client connecting to the server in a TLS client/server mutual-authentication setup.
- openSUSE-SU-2020:0031
- openSUSE-SU-2020:0031
- https://github.com/proftpd/proftpd/issues/861
- https://github.com/proftpd/proftpd/issues/861
- [debian-lts-announce] 20191130 [SECURITY] [DLA 2018-1] proftpd-dfsg security update
- [debian-lts-announce] 20191130 [SECURITY] [DLA 2018-1] proftpd-dfsg security update
- FEDORA-2019-65a983b8b6
- FEDORA-2019-65a983b8b6
- FEDORA-2019-bfacf1e958
- FEDORA-2019-bfacf1e958
- GLSA-202003-35
- GLSA-202003-35
- https://www.oracle.com/security-alerts/cpuapr2020.html
- https://www.oracle.com/security-alerts/cpuapr2020.html
Modified: 2024-11-21
CVE-2019-19270
An issue was discovered in tls_verify_crl in ProFTPD through 1.3.6b. Failure to check for the appropriate field of a CRL entry (checking twice for subject, rather than once for subject and once for issuer) prevents some valid CRLs from being taken into account, and can allow clients whose certificates have been revoked to proceed with a connection to the server.
Modified: 2024-11-21
CVE-2020-9272
ProFTPD 1.3.7 has an out-of-bounds (OOB) read vulnerability in mod_cap via the cap_text.c cap_to_text function.
- openSUSE-SU-2020:0273
- openSUSE-SU-2020:0273
- https://cert-portal.siemens.com/productcert/pdf/ssa-679335.pdf
- https://cert-portal.siemens.com/productcert/pdf/ssa-679335.pdf
- https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
- https://github.com/proftpd/proftpd/issues/902
- https://github.com/proftpd/proftpd/issues/902
- GLSA-202003-35
- GLSA-202003-35
Closed vulnerabilities
Modified: 2024-11-21
CVE-2021-22881
The Host Authorization middleware in Action Pack before 6.1.2.1, 6.0.3.5 suffers from an open redirect vulnerability. Specially crafted `Host` headers in combination with certain "allowed host" formats can cause the Host Authorization middleware in Action Pack to redirect users to a malicious website. Impacted applications will have allowed hosts with a leading dot. When an allowed host contains a leading dot, a specially crafted `Host` header can be used to redirect to a malicious website.
- [oss-security] 20210505 [CVE-2021-22903] Possible Open Redirect Vulnerability in Action Pack
- [oss-security] 20210505 [CVE-2021-22903] Possible Open Redirect Vulnerability in Action Pack
- [oss-security] 20210819 [CVE-2021-22942] Possible Open Redirect in Host Authorization Middleware
- [oss-security] 20210819 [CVE-2021-22942] Possible Open Redirect in Host Authorization Middleware
- [oss-security] 20211214 [CVE-2021-44528] Possible Open Redirect in Host Authorization Middleware
- [oss-security] 20211214 [CVE-2021-44528] Possible Open Redirect in Host Authorization Middleware
- https://benjamin-bouchet.com/cve-2021-22881-faille-de-securite-dans-le-middleware-hostauthorization/
- https://benjamin-bouchet.com/cve-2021-22881-faille-de-securite-dans-le-middleware-hostauthorization/
- https://discuss.rubyonrails.org/t/cve-2021-22881-possible-open-redirect-in-host-authorization-middleware/77130
- https://discuss.rubyonrails.org/t/cve-2021-22881-possible-open-redirect-in-host-authorization-middleware/77130
- https://hackerone.com/reports/1047447
- https://hackerone.com/reports/1047447
- FEDORA-2021-b571fca1b8
- FEDORA-2021-b571fca1b8
Modified: 2024-11-21
CVE-2021-22942
A possible open redirect vulnerability in the Host Authorization middleware in Action Pack >= 6.0.0 that could allow attackers to redirect users to a malicious website.
- [oss-security] 20211214 [CVE-2021-44528] Possible Open Redirect in Host Authorization Middleware
- [oss-security] 20211214 [CVE-2021-44528] Possible Open Redirect in Host Authorization Middleware
- https://security.netapp.com/advisory/ntap-20240202-0005/
- https://security.netapp.com/advisory/ntap-20240202-0005/
- https://weblog.rubyonrails.org/2021/8/19/Rails-6-0-4-1-and-6-1-4-1-have-been-released/
- https://weblog.rubyonrails.org/2021/8/19/Rails-6-0-4-1-and-6-1-4-1-have-been-released/
- DSA-5372
- DSA-5372