Your message dated Wed, 24 Aug 2022 23:25:57 +0300
with message-id <YwaJVRiDt9fEbvlz@localhost>
and subject line Re: Bug#1014807: ruby-jmespath: CVE-2022-32511
has caused the Debian Bug report #1014807,
regarding ruby-jmespath: CVE-2022-32511
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 ow...@bugs.debian.org
immediately.)


-- 
1014807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jmespath
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for ruby-jmespath.

CVE-2022-32511[0]:
| jmespath.rb (aka JMESPath for Ruby) before 1.6.1 uses JSON.load in a
| situation where JSON.parse is preferable.

https://github.com/jmespath/jmespath.rb/pull/55
https://github.com/jmespath/jmespath.rb/commit/e8841280053a9d9a0c90f36223f926c8b9e4ec49
 (v1.6.1)

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-2022-32511
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32511

Please adjust the affected versions in the BTS as needed.

--- End Message ---
--- Begin Message ---
Version: 1.6.1-1

On Tue, Jul 12, 2022 at 12:05:57PM +0200, Moritz Mühlenhoff wrote:
> Source: ruby-jmespath
> X-Debbugs-CC: t...@security.debian.org
> Severity: grave
> Tags: security
> 
> Hi,
> 
> The following vulnerability was published for ruby-jmespath.
> 
> CVE-2022-32511[0]:
> | jmespath.rb (aka JMESPath for Ruby) before 1.6.1 uses JSON.load in a
> | situation where JSON.parse is preferable.
>... 

This was recently fixed in unstable.

cu
Adrian

--- End Message ---

Reply via email to