Bug 1729079 - CVE-2019-12594 dosbox: running a malicious executable in the emulator could result in the execution of arbitrary code [fedora-all]
Summary: CVE-2019-12594 dosbox: running a malicious executable in the emulator could r...
Alias: None
Product: Fedora
Classification: Fedora
Component: dosbox
Version: 30
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: François Cami
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: CVE-2019-12594
TreeView+ depends on / blocked
Reported: 2019-07-11 11:09 UTC by Marian Rehak
Modified: 2019-10-25 10:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2019-10-25 10:58:54 UTC
Type: ---

Attachments (Terms of Use)

Description Marian Rehak 2019-07-11 11:09:17 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Comment 1 Marian Rehak 2019-07-11 11:09:19 UTC
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)

# low, medium, high, urgent (required)

# testing, stable

# Bug numbers: 1234,9876

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds

# Automatically close bugs when this marked as stable

# Suggest that users restart after update


Additionally, you may opt to use the bodhi web interface to submit updates:


Comment 2 François Cami 2019-10-10 21:04:59 UTC
Taking, will fix.

Comment 3 François Cami 2019-10-10 21:24:18 UTC
Upstream changelog for dosbox-0.74-3 is at: https://sourceforge.net/projects/dosbox/files/dosbox/0.74-3/

Changelog extract of 0.74-3:
A security release for DOSBox 0.74:
- Fixed that a very long line inside a bat file would overflow the parsing 
  buffer (CVE-2019-7165 by Alexandre Bartel)
- Added a basic permission system so that a program running inside DOSBox 
  can't access the contents of /proc (e.g. /proc/self/mem) when / or /proc
  were (to be) mounted (CVE-2019-12594 by Alexandre Bartel)  
- Several other fixes for out of bounds access and buffer overflows.

I've just double-checked the tarball for DOSBox 0.74-3 and it contains both:
which are mentioned as the diffs to backport for both recent CVEs in https://sourceforge.net/p/dosbox/bugs/508/

Fedora 30 got the complete DOSBox 0.74-3 update on 2019-7-4:
and it hit stable on 2019-7-8.

Comment 5 Marian Rehak 2019-10-23 13:23:22 UTC

Yes this checks out, thank you for noticing and I'm sorry for the confusion.

I created fedora-29 only tracker for this issue, which has the older version dosbox-0.74.2-2.

Best regards.

Comment 6 François Cami 2019-10-23 13:59:46 UTC
So it's good to track CVEs across multiple branches, but Fedora 29 already has the fix in updates-testing:
just like EPEL7 has:

Both would update these distributions to 0.74-3.
Both were opened on 2019-7-4 (same day as the update for f30.
They are both missing karma proving there has been no community testing.

Could you make sure to check available updates in Bodhi before opening new bugs please?

Comment 7 Marian Rehak 2019-10-25 10:51:41 UTC
Thank you for explaining that and for the link. I surely will try to check that before opening new trackers!

Comment 8 François Cami 2019-10-25 10:58:54 UTC
Thanks Marian, much appreciated.
I'm closing this bug too.

Note You need to log in before you can comment on or make changes to this bug.