More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2284252 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2284252,2284254 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
This has been fixed since 3.1.7, see https://github.com/stephane/libmodbus/issues/748 b4ef4c17d618eba0adccc4c7d9e9a1ef809fc9b6 is the first bad commit commit b4ef4c17d618eba0adccc4c7d9e9a1ef809fc9b6 Author: Michael Heimpold <mhei> Date: Sat Jan 8 20:00:50 2022 +0100 modbus_reply: fix copy & paste error in sanity check (fixes #614) While handling MODBUS_FC_WRITE_AND_READ_REGISTERS, both address offsets must be checked, i.e. the read and the write address must be within the mapping range. At the moment, only the read address was considered, it looks like a simple copy and paste error, so let's fix it. Signed-off-by: Michael Heimpold <mhei> src/modbus.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) version 3.1.7 is in EPEL8, EPEL9, Fedora 39, and Fedora 40, so no current releases are affected. Closing NOTABUG because it has already been fixed.