Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚨 [security] [src/api - 2.10] Update nokogiri: 1.10.4 β†’ 1.10.5 (patch) #8727

Merged
merged 1 commit into from
Nov 18, 2019

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Nov 17, 2019


🚨 Your version of nokogiri has known security vulnerabilities 🚨

Advisory: CVE-2019-13117
Disclosed: October 31, 2019
URL: https://github.com/sparklemotion/nokogiri/issues/1943

Nokogiri gem, via libxslt, is affected by multiple vulnerabilities

Nokogiri v1.10.5 has been released.

This is a security release. It addresses three CVEs in upstream libxml2,
for which details are below.

If you're using your distro's system libraries, rather than Nokogiri's
vendored libraries, there's no security need to upgrade at this time,
though you may want to check with your distro whether they've patched this
(Canonical has patched Ubuntu packages). Note that libxslt 1.1.34 addresses
these vulnerabilities.

Full details about the security update are available in Github Issue
[#1943] #1943.


CVE-2019-13117

https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-13117.html

Priority: Low

Description: In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings
could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This
could allow an attacker to discern whether a byte on the stack contains the
characters A, a, I, i, or 0, or any other character.

Patched with commit https://gitlab.gnome.org/GNOME/libxslt/commit/c5eb6cf3aba0af048596106ed839b4ae17ecbcb1


CVE-2019-13118

https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-13118.html

Priority: Low

Description: In numbers.c in libxslt 1.1.33, a type holding grouping characters of an
xsl:number instruction was too narrow and an invalid character/length
combination could be passed to xsltNumberFormatDecimal, leading to a read
of uninitialized stack data

Patched with commit https://gitlab.gnome.org/GNOME/libxslt/commit/6ce8de69330783977dd14f6569419489875fb71b


CVE-2019-18197

https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-18197.html

Priority: Medium

Description: In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't
reset under certain circumstances. If the relevant memory area happened to
be freed and reused in a certain way, a bounds check could fail and memory
outside a buffer could be written to, or uninitialized data could be
disclosed.

Patched with commit https://gitlab.gnome.org/GNOME/libxslt/commit/2232473733b7313d67de8836ea3b29eec6e8e285


🚨 We recommend to merge and deploy this update as soon as possible! 🚨

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ nokogiri (1.10.4 β†’ 1.10.5) Β· Repo Β· Changelog

Release Notes

1.10.5

1.10.5 / 2019-10-31

Dependencies

  • [MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10
  • [MRI] vendored libxslt is updated from 1.1.33 to 1.1.34

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 7 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added 2.10 depfu PRs from our dependency update bot security Pull requests that address a security vulnerability labels Nov 17, 2019
@codecov
Copy link

codecov bot commented Nov 17, 2019

Codecov Report

Merging #8727 into 2.10 will decrease coverage by 0.03%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##             2.10    #8727      +/-   ##
==========================================
- Coverage   90.77%   90.74%   -0.04%     
==========================================
  Files         501      501              
  Lines       21381    21381              
==========================================
- Hits        19409    19402       -7     
- Misses       1972     1979       +7

@coolo
Copy link
Member

coolo commented Nov 18, 2019

the security tag comes purely from the bundled libraries we don't use

@DavidKang DavidKang merged commit a6b71ac into 2.10 Nov 18, 2019
@DavidKang DavidKang deleted the depfu/update/srcapi-2.10/nokogiri-1.10.5 branch November 18, 2019 08:34
@coolo
Copy link
Member

coolo commented Nov 18, 2019

https://build.opensuse.org/package/show/OBS:Server:2.10:Staging/obs-server is not triggered by tokens, so someone needs to run the services.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.10 depfu PRs from our dependency update bot security Pull requests that address a security vulnerability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants