Summary: | <app-editors/{vim,gvim}-8.0.0386: two integer overflow | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | Agostino Sarubbo <ago> |
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | asl, joshuabaergen, vim |
Priority: | Normal | Flags: | stable-bot:
sanity-check+
|
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | B2 [glsa cve] | ||
Package list: |
=app-editors/vim-8.0.0386
=app-editors/vim-core-8.0.0386
=app-editors/gvim-8.0.0386
|
Runtime testing required: | --- |
Description
Agostino Sarubbo
![]() A newer version of vim is already in the tree. If you want to stabilize that, go ahead. An automated check of this bug failed - repoman reported dependency errors (105 lines truncated):
> dependency.bad app-editors/vim/vim-8.0.0386.ebuild: DEPEND: alpha(default/linux/alpha/13.0) ['~app-editors/vim-core-8.0.0386']
> dependency.bad app-editors/vim/vim-8.0.0386.ebuild: RDEPEND: alpha(default/linux/alpha/13.0) ['~app-editors/vim-core-8.0.0386']
> dependency.bad app-editors/vim/vim-8.0.0386.ebuild: DEPEND: alpha(default/linux/alpha/13.0/desktop) ['~app-editors/vim-core-8.0.0386']
amd64 stable arm arm64 ppc ppc64 stable. Does gvim need to be updated as well? (In reply to Joshua Baergen from comment #5) > Does gvim need to be updated as well? Yes, good catch. Re-adding arches. Stable on alpha. Hello, gvim needs to get its stable keyword too, right now you can't emerge it, it's blocked by vim-core. amd64 stable x86 stable sparc stable Stable for HPPA PPC64. arm stable ppc stable. gvim isn't keyworded for arm64, rest was stabled in the first round. ia64 stable. Maintainer(s), please cleanup. Security, please add it to the existing request, or file a new one. Maintainer(s), Thank you for your work. New GLSA Request filed. Maintainer(s), please drop the vulnerable version(s). Maintainer(s), please drop the vulnerable version(s). Cleanup PR: https://github.com/gentoo/gentoo/pull/4847 Thanks Whissi for the PR! Security please proceed. This issue was resolved and addressed in GLSA 201706-26 at https://security.gentoo.org/glsa/201706-26 by GLSA coordinator Kristian Fiskerstrand (K_F). |