- Update from version 4.18.4 to 4.18.5
- Update of rootfile not required
- Changelog
4.18.5
This is a security release in order to address the following defects:
o CVE-2022-2127: When winbind is used for NTLM authentication, a maliciously
crafted request can trigger an out-of-bounds read in winbind
and possibly crash it.
https://www.samba.org/samba/security/CVE-2022-2127.html
o CVE-2023-3347: SMB2 packet signing is not enforced if an admin configured
"server signing = required" or for SMB2 connections to Domain
Controllers where SMB2 packet signing is mandatory.
https://www.samba.org/samba/security/CVE-2023-3347.html
o CVE-2023-34966: An infinite loop bug in Samba's mdssvc RPC service for
Spotlight can be triggered by an unauthenticated attacker by
issuing a malformed RPC request.
https://www.samba.org/samba/security/CVE-2023-34966.html
o CVE-2023-34967: Missing type validation in Samba's mdssvc RPC service for
Spotlight can be used by an unauthenticated attacker to
trigger a process crash in a shared RPC mdssvc worker process.
https://www.samba.org/samba/security/CVE-2023-34967.html
o CVE-2023-34968: As part of the Spotlight protocol Samba discloses the server-
side absolute path of shares and files and directories in
search results.
https://www.samba.org/samba/security/CVE-2023-34968.html
o Ralph Boehme <slow@samba.org>
* BUG 15072: CVE-2022-2127.
* BUG 15340: CVE-2023-34966.
* BUG 15341: CVE-2023-34967.
* BUG 15388: CVE-2023-34968.
* BUG 15397: CVE-2023-3347.
o Volker Lendecke <vl@samba.org>
* BUG 15072: CVE-2022-2127.
o Stefan Metzmacher <metze@samba.org>
* BUG 15418: Secure channel faulty since Windows 10/11 update 07/2023.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
The Linux firmware microcode patches require Git to apply binary
patches as they are not supported by patch(8).
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
- Update from version 9.3p1 to 9.3p2
- Update of rootfile not required
- Changelog
9.3p2 (2023-07-19)
This release fixes a security bug.
Security
Fix CVE-2023-38408 - a condition where specific libaries loaded via
ssh-agent(1)'s PKCS#11 support could be abused to achieve remote
code execution via a forwarded agent socket if the following
conditions are met:
* Exploitation requires the presence of specific libraries on
the victim system.
* Remote exploitation requires that the agent was forwarded
to an attacker-controlled system.
Exploitation can also be prevented by starting ssh-agent(1) with an
empty PKCS#11/FIDO allowlist (ssh-agent -P '') or by configuring
an allowlist that contains only specific provider libraries.
This vulnerability was discovered and demonstrated to be exploitable
by the Qualys Security Advisory team.
In addition to removing the main precondition for exploitation,
this release removes the ability for remote ssh-agent(1) clients
to load PKCS#11 modules by default (see below).
Potentially-incompatible changes
* ssh-agent(8): the agent will now refuse requests to load PKCS#11
modules issued by remote clients by default. A flag has been added
to restore the previous behaviour "-Oallow-remote-pkcs11".
Note that ssh-agent(8) depends on the SSH client to identify
requests that are remote. The OpenSSH >=8.9 ssh(1) client does
this, but forwarding access to an agent socket using other tools
may circumvent this restriction.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
- Update from version 1.9.14 to 1.9.14p2
- Update of rootfile not required
- Changelog
1.9.14p2
* Fixed a crash on Linux systems introduced in version 1.9.14 when
running a command with a NULL argv[0] if "log_subcmds" or
"intercept" is enabled in sudoers.
* Fixed a problem with "stair-stepped" output when piping or
redirecting the output of a sudo command that takes user input.
* Fixed a bug introduced in sudo 1.9.14 that affects matching
sudoers rules containing a Runas_Spec with an empty Runas user.
These rules should only match when sudo's -g option is used but
were matching even without the -g option. GitHub issue #290.
1.9.14p1
* Fixed an invalid free bug in sudo_logsrvd that was introduced
in version 1.9.14 which could cause sudo_logsrvd to crash.
* The sudoers plugin no longer tries to send the terminal name
to the log server when no terminal is present. This bug was
introduced in version 1.9.14.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
This change will make sure that dehydrated will continue if (re-)issuing
one or more certificate fails.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>
Since the update is not built on the day when people install it, we will
ship an outdated database. For updates, where the firewall is being
reloaded or rebooted, we will have an old database in place until the
next database update job runs.
Secondly, the data is 33 MiB in size, which is useless data shipped as
every system will already have a database that is very likely to be more
recent.
In this update, we are not shipping the location database again, but I
wanted to add this change so it does not get lost next time.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>
This changes the old "diff" algorithm that we needed to have before
Unbound was able to reload its own configuration.
Now, it can do this even without dropping the cache. This should
hopefully perform much better and be more reliable than the old way.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Acked-by: Peter Müller <peter.mueller@ipfire.org>
- changes `interface` to `pcap_interface` in pmacct.conf file.
- thank you to @iptom for finding and reporting the issue and
to many others for pitching in and helping debug!
Signed-off-by: Jon Murphy <jon.murphy@ipfire.org>
Originally announced for Core Update 176, this step was postponed until
Core Update 177 due to my fault of having shipped all necessary
dependencies for OpenSSL 3.x in Core Update 175 properly.
Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
Reviewed-by: Michael Tremer <michael.tremer@ipfire.org>
For details see:
http://lists.squid-cache.org/pipermail/squid-users/2023-July/025929.html
"The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-6.1 release!
This release is we believe, stable enough for general production use.
Support for Squid-5 bug fixes has now officially ceased. Bugs in 5.x
will continue to be fixed, however the fixes will be added to the 6.x
series. All users of Squid-5.x are encouraged to plan for upgrades."
And:
http://www.squid-cache.org/Versions/v6/RELEASENOTES.html
v6 is running since 6.0.1 here in production use without any seen problems...
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>
- When cups is installed (including when doing a Core Update that includes a cups update)
the 5 min delay for starting cups means that it has not restarted by the time that the
reboot for the CU has been started. There are then error messages that say that cups
couldn't be stopped as it was not running.
- When a normal reboot is carried out withoutr any update of cups then the startup has
no delay and it starts without any trouble.
- This patch removes the 300 secs delay from the start_service line in the install.sh paks
file.
- The PAK_VER is bumped to ensure that this change is shipped
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>
- Removal of lfs file
- Removal of rootfile
- Removal of backup includes file
- Removal of three patches
- Removal of paks files
- Adjustment of make.sh to remove squidclamav
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>
- Update from version 20230404 to 20230625
- Update of rootfile carried out based on Peter Mueller's description from last
linux-firmware update.
- It would be good to have it checked that my results are in line with what they should be.
- Changelog
For changes see the commits in the git repo
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
- Patch provided by bug reporter. Here is the description of the problem from the bug.
First I discovered that the helper only sometimes throwing the error and quits even
for the same values and queries. Also the timespan until the error happens was quite
different for every restart of squid (minutes to hours). And it does not depend on
the traffic on the proxy, even one connection could cause a crash while ten or
hundrets won't. After a few days of testing different solutions and done a lot of
debugging, redesigning the function did not fully solve the problem. Such standard
things like checking the result variable for NULL (or it's equivalent "is None" in
python) before evaluating it's subfunction produces the exact same error message. But
with that knowledge it more and more turns out that python3 sometimes 'detects' the
local return variable if it was a misused global. So for a full fix, the return
variable also has to be initialized that python3 won't detect it's usage as an
'UnboundLocalError' to succesfully fix this bug.
- LFS file updated to run patch before copying helper into place.
- Update of rootfile not needed.
- Bug reporter has been requested to raise this issue at the git repo for squid-asnbl.
Fixes: Bug#13023
Tested-by: Nicolas Pӧhlmann <business@hardcoretec.com>
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
- Update from version 1.9.13p3 to 1.9.14
- Update of rootfile not required
- Changelog
Significant change is that use_pty is now defined as the default setting.
This parameter was made available back in version 1.8.0 but not as default.
It was implemented in response to a variety of CVE's related to being vulnerable to
privilege escalation via TIOCSTI and/or lesser-known TIOCLINUX command injection.
Apparently it was not made default as that would change the way that sudo worked.
As various existing bugs have been resolved it has now been declared by the sudo devs
that now sudo with a pseudo terminal works close to the same as with the users terminal
Hence in this version the use of the pseudo terminal is now default.
See https://github.com/sudo-project/sudo/issues/258 for more details.
1.9.14
Fixed a bug where if the intercept or log_subcmds sudoers option was enabled and a
sub-command was run where the first entry of the argument vector didn't match the
command being run. This resulted in commands like sudo su - being killed due to the
mismatch. Bug #1050.
The sudoers plugin now canonicalizes command path names before matching (where
possible). This fixes a bug where sudo could execute the wrong path if there are
multiple symbolic links with the same target and the same base name in sudoers that a
user is allowed to run. GitHub issue #228.
Improved command matching when a chroot is specified in sudoers. The sudoers plugin
will now change the root directory id needed before performing command matching.
Previously, the root directory was simply prepended to the path that was being
processed.
When NETGROUP_BASE is set in the ldap.conf file, sudo will now perform its own
netgroup lookups of the host name instead of using the system innetgr(3) function.
This guarantees that user and host netgroup lookups are performed using the same LDAP
server (or servers).
Fixed a bug introduced in sudo 1.9.13 that resulted in a missing " ; " separator
between environment variables and the command in log entries.
The visudo utility now displays a warning when it ignores a file in an include dir
such as /etc/sudoers.d.
When running a command in a pseudo-terminal, sudo will initialize the terminal
settings even if it is the background process. Previously, sudo only initialized the
pseudo-terminal when running in the foreground. This fixes an issue where a program
that checks the window size would read the wrong value when sudo was running in the
background.
Fixed a bug where only the first two digits of the TSID field being was logged.
Bug #1046.
The use_pty sudoers option is now enabled by default. To restore the historic behavior
where a command is run in the user's terminal, add Defaults !use_pty to the sudoers
file. GitHub issue #258.
Sudo's -b option now works when the command is run in a pseudo-terminal.
When disabling core dumps, sudo now only modifies the soft limit and leaves the hard
limit as-is. This avoids problems on Linux when sudo does not have CAP_SYS_RESOURCE,
which may be the case when run inside a container. GitHub issue #42.
Sudo configuration file paths have been converted to colon-separated lists of paths.
This makes it possible to have configuration files on a read-only file system while
still allowing for local modifications in a different (writable) directory. The new
--enable-adminconf configure option can be used to specify a directory that is
searched for configuration files in preference to the sysconfdir (which is usually
/etc).
The intercept_verify sudoers option is now only applied when the intercept option is
set in sudoers. Previously, it was also applied when log_subcmds was enabled.
The NETGROUP_QUERY ldap.conf parameter can now be disabled for LDAP servers that do
not support querying the nisNetgroup object by its nisNetgroupTriple attribute, while
still allowing sudo to query the LDAP server directly to determine netgroup
membership.
Fixed a long-standing bug where a sudoers rule without an explicit runas list allowed
the user to run a command as root and any group instead of just one of the groups
that root is a member of. For example, a rule such as myuser ALL = ALL would permit
sudo -u root -g othergroup even if root did not belong to othergroup.
Fixed a bug where a sudoers rule with an explicit runas list allowed a user to run
sudo commands as themselves. For example, a rule such as myuser ALL = (root) ALL,
myuser should only allow commands to be run as root (optionally using one of root's
groups). However, the rule also allowed the user to run sudo -u myuser -g myuser
command.
Fixed a bug that prevented the user from specifying a group on the command line via
sudo -g if the rule's Runas_Spec contained a Runas_Alias.
Sudo now requires a C99 compiler due to the use of flexible array members.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>
