unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Leo Famulari <leo@famulari.name>, 27462@debbugs.gnu.org
Subject: bug#27462: OCaml CVE-2015-8869
Date: Sat, 24 Jun 2017 10:25:52 +1000	[thread overview]
Message-ID: <faae92d6-1f30-9e7f-4e56-f7c69a794388@uq.edu.au> (raw)
In-Reply-To: <20170623164129.GA4417@jasmine.lan>

Hi Leo,


On 24/06/17 02:41, Leo Famulari wrote:
> Our package ocaml-4.01 is vulnerable to CVE-2015-8869, which we patched
> in the primary ocaml package in April 2016. Unfortunately, this patch
> was not included when the ocaml-4.01 package was created in January
> 2017.
>
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8869
>
> Do we need this older version of OCaml? If so, we need a volunteer to
> maintain it.

Thanks for pointing this out. AFAIK OCaml 4.01 is really only used to 
build pplacer, a bioinformatics program. I was planning on submitting 3 
further bioinformatic packages soon which rely on pplacer, however.

I'm not sure I have the bandwidth to backport patches to such an old 
release, especially since the OCaml maintainers do not appear to be 
either, AFAICS.

This is a little frustrating, but perhaps they should be removed. WDYT?

ben

  reply	other threads:[~2017-06-24  0:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 16:41 bug#27462: OCaml CVE-2015-8869 Leo Famulari
2017-06-24  0:25 ` Ben Woodcroft [this message]
2017-06-24 16:03   ` Leo Famulari
2019-01-31 16:57 ` Andreas Enge
2019-01-31 17:21   ` Andreas Enge
2019-01-31 17:30     ` Julien Lepiller
2019-02-19 22:17       ` Andreas Enge
2019-02-20  8:39         ` Julien Lepiller
2019-02-20 11:27           ` Andreas Enge
2019-01-31 17:26   ` swedebugia
2019-07-05 12:12 ` Julien Lepiller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=faae92d6-1f30-9e7f-4e56-f7c69a794388@uq.edu.au \
    --to=b.woodcroft@uq.edu.au \
    --cc=27462@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).