It was discovered that an integer overflow could be triggered in Libksba
when decoding certain data. An attacker could use this issue to cause a
denial of service (application crash) or possibly execute arbitrary code.
MVPower CCTV DVR models, including TV-7104HE 1.8.4 115215B9 and TV7108HE, contain a web shell that is accessible via a /shell URI. A remote unauthenticated attacker can execute arbitrary operating system commands as root. This vulnerability has also been referred to as the “JAWS webserver RCE” because of the easily identifying HTTP response server field. Other firmware versions, at least from 2014 through 2019, can be affected. This was exploited in the wild in 2017 through 2022.
D-Link DSL-2750B devices before 1.05 allow remote unauthenticated command injection via the login.cgi cli parameter, as exploited in the wild in 2016 through 2022.
git-2.38.1-1.fc35
Upstream update including security & bug fixes as well as feature enhancements.
From the upstream release notes:
When relying on the –local clone optimization, Git dereferences
symbolic links in the source repository before creating hardlinks
(or copies) of the dereferenced link in the destination repository.
This can lead to surprising behavior where arbitrary files are
present in a repository’s $GIT_DIR when cloning from a malicious
repository.
Git will no longer dereference symbolic links via the –local
clone mechanism, and will instead refuse to clone repositories that
have symbolic links present in the $GIT_DIR/objects directory.
Additionally, the value of protocol.file.allow is changed to be
“user” by default.
An overly-long command string given to git shell can result in
overflow in split_cmdline(), leading to arbitrary heap writes and
remote code execution when git shell is exposed and the directory
$HOME/git-shell-commands exists.
git shell is taught to refuse interactive commands that are
longer than 4MiB in size. split_cmdline() is hardened to reject
inputs larger than 2GiB.
Credit for finding CVE-2022-39253 goes to Cory Snider of Mirantis. The
fix was authored by Taylor Blau, with help from Johannes Schindelin.
Credit for finding CVE-2022-39260 goes to Kevin Backhouse of GitHub.
The fix was authored by Kevin Backhouse, Jeff King, and Taylor Blau.
git-2.38.1-1.fc36
Upstream update including security & bug fixes as well as feature enhancements.
From the upstream release notes:
When relying on the –local clone optimization, Git dereferences
symbolic links in the source repository before creating hardlinks
(or copies) of the dereferenced link in the destination repository.
This can lead to surprising behavior where arbitrary files are
present in a repository’s $GIT_DIR when cloning from a malicious
repository.
Git will no longer dereference symbolic links via the –local
clone mechanism, and will instead refuse to clone repositories that
have symbolic links present in the $GIT_DIR/objects directory.
Additionally, the value of protocol.file.allow is changed to be
“user” by default.
An overly-long command string given to git shell can result in
overflow in split_cmdline(), leading to arbitrary heap writes and
remote code execution when git shell is exposed and the directory
$HOME/git-shell-commands exists.
git shell is taught to refuse interactive commands that are
longer than 4MiB in size. split_cmdline() is hardened to reject
inputs larger than 2GiB.
Credit for finding CVE-2022-39253 goes to Cory Snider of Mirantis. The
fix was authored by Taylor Blau, with help from Johannes Schindelin.
Credit for finding CVE-2022-39260 goes to Kevin Backhouse of GitHub.
The fix was authored by Kevin Backhouse, Jeff King, and Taylor Blau.
git-2.38.1-1.fc37
Upstream update including security & bug fixes as well as feature enhancements.
From the upstream release notes:
When relying on the –local clone optimization, Git dereferences
symbolic links in the source repository before creating hardlinks
(or copies) of the dereferenced link in the destination repository.
This can lead to surprising behavior where arbitrary files are
present in a repository’s $GIT_DIR when cloning from a malicious
repository.
Git will no longer dereference symbolic links via the –local
clone mechanism, and will instead refuse to clone repositories that
have symbolic links present in the $GIT_DIR/objects directory.
Additionally, the value of protocol.file.allow is changed to be
“user” by default.
An overly-long command string given to git shell can result in
overflow in split_cmdline(), leading to arbitrary heap writes and
remote code execution when git shell is exposed and the directory
$HOME/git-shell-commands exists.
git shell is taught to refuse interactive commands that are
longer than 4MiB in size. split_cmdline() is hardened to reject
inputs larger than 2GiB.
Credit for finding CVE-2022-39253 goes to Cory Snider of Mirantis. The
fix was authored by Taylor Blau, with help from Johannes Schindelin.
Credit for finding CVE-2022-39260 goes to Kevin Backhouse of GitHub.
The fix was authored by Kevin Backhouse, Jeff King, and Taylor Blau.
dotnet3.1-3.1.424-1.fc35
This is the October 2022 release of .NET Core 3.1
This updates .NET Core 3.1 SDK to 3.1.424 and Runtime to 3.1.30.
This includes fixes for CVE-2022-41032
dotnet3.1-3.1.424-1.fc36
This is the October 2022 release of .NET Core 3.1
This updates .NET Core 3.1 SDK to 3.1.424 and Runtime to 3.1.30.
This includes fixes for CVE-2022-41032
FortiGuard Labs is aware of a report that a new ransomware strain called Prestige was being distributed in an attack campaign targeting Ukraine and Poland. The ransomware encrypts files on a compromised machine and adds a “.enc” file extension to the affected files.Why is this Significant?This is significant because Prestige ransomware is one of the few ransomware strains being distributed to Ukraine, as well as Poland, who is a known ally of Ukraine.How Widespread is the Attack?According to Microsoft, Prestige ransomware was distributed to organizations in Ukraine and Poland.What is Prestige Ransomware?Prestige ransomware encrypts files on a compromised machine and adds a “.enc” file extension to the affected files.The ransomware leaves a ransom note in “README”, which asks the victim to contact the attacker by sending an email to the address for file decryption. The ransom note also has an unique ID, which acts as a victim identifier. It also deletes the shadow copies via vssadmin, which inhibits the victim’s ability to recover files.How was Prestige Ransomware Distributed?While the infection vector has not been identified, Microsoft reported that the attacker used several legitimate Windows and open-source tools for remote code execution, privilege execution and credential exfiltration prior to the ransomware deployment.What is the Status of Protection?FortiGuard Labs detects an available Prestige ransomware sample with the following AV coverage:• W32/Filecoder.OMM!tr.ransom
Several vulnerabilities were discovered in Squid, a fully featured web
proxy cache, which could result in exposure of sensitive information in
the cache manager (CVE-2022-41317),
or denial of service or information disclosure if Squid is configured to
negotiate authentication with the SSPI and SMB authentication helpers
(CVE-2022-41318).
