Your message dated Mon, 7 Aug 2023 10:42:22 +0100
with message-id <[email protected]>
and subject line Re: Bug#1031732: iortcw: CVE-2019-25104
has caused the Debian Bug report #1031732,
regarding iortcw: CVE-2019-25104
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1031732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031732
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: iortcw
X-Debbugs-CC: [email protected]
Severity: important
Tags: security
Hi,
The following vulnerability was published for rtcwcoop, which seems
to be a fork of iortcw, but the patches don't seem to have flown back?
CVE-2019-25104[0]:
| A vulnerability has been found in rtcwcoop 1.0.2 and classified as
| problematic. Affected by this vulnerability is the function
| AICast_ScriptLoad of the file code/game/ai_cast_script.c of the
| component Team Command Handler. The manipulation leads to denial of
| service. The name of the patch is
| f2cd18bc2e1cbca8c4b78bee9c392272bd5f42ac. It is recommended to apply a
| patch to fix this issue. The identifier VDB-221485 was assigned to
| this vulnerability.
https://github.com/rtcwcoop/rtcwcoop/pull/45
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2019-25104
https://www.cve.org/CVERecord?id=CVE-2019-25104
Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
On Tue, 21 Feb 2023 at 20:42:55 +0100, Moritz Muehlenhoff wrote:
> On Tue, Feb 21, 2023 at 03:32:01PM +0000, Simon McVittie wrote:
> > I'm also not at all sure that iortcw is even vulnerable to this.
>
> Please adjust the severity (and or close if not applicable at all) as
> necessary
Based on discussion on https://github.com/iortcw/iortcw/issues/174, this
is specific to rtcwcoop, which is a fork of iortcw rather than the other
way round. In iortcw multiplayer, the affected code is unreachable, and
in iortcw single-player, being able to crash the game through resource
exhaustion is not a security issue (the player can only hurt themself,
not others).
smcv
--- End Message ---
