Security
Headlines
HeadlinesLatestCVEs

Tag

#ubuntu

CVE-2021-46508: Assertion `i < parts_cnt' failed at src/mjs_bcode.c:121: struct mjs_bcode_part *mjs_bcode_part_get_by_offset(struct mjs *, size_t). · Issue #188 · cesanta/mjs

There is an Assertion `i < parts_cnt' failed at src/mjs_bcode.c in Cesanta MJS v2.20.0.

CVE
#ubuntu#linux#js#git
CVE-2021-46517: Assertion `mjs_stack_size(&mjs->scopes) > 0' failed src/mjs_exec.c:725: mjs_execute. · Issue #184 · cesanta/mjs

There is an Assertion `mjs_stack_size(&mjs->scopes) > 0' failed at src/mjs_exec.c in Cesanta MJS v2.20.0.

CVE-2021-46515: Assertion `mjs_stack_size(&mjs->scopes) >= scopes_len' failed at src/mjs_exec.c:949: mjs_execute. · Issue #186 · cesanta/mjs

There is an Assertion `mjs_stack_size(&mjs->scopes) >= scopes_len' failed at src/mjs_exec.c in Cesanta MJS v2.20.0.

CVE-2022-22852: CVE-2022-22852/CVE-2022-22852.md at main · Sant268/CVE-2022-22852

A Stored Cross Site Scripting (XSS) vulnerability exists in Sourcecodtester Hospital's Patient Records Management System 1.0 via the description parameter in room_list.

CVE-2022-22850: CVE-2022-22850/CVE-2022-22850.md at main · Sant268/CVE-2022-22850

A Stored Cross Site Scripting (XSS) vulnerability exists in Sourcecodtester Hospital's Patient Records Management System 1.0 via the description parameter in room_types.

CVE-2022-0368: Out-of-bounds Read in vim

Out-of-bounds Read in GitHub repository vim/vim prior to 8.2.

CVE-2022-0368: Out-of-bounds Read in vim

Out-of-bounds Read in Conda vim prior to 8.2.

CVE-2022-22851: Create CVE-2022-22851.md · Sant268/CVE-2022-22851@1738137

A Stored Cross Site Scripting (XSS) vulnerability exists in Sourcecodtester Hospital's Patient Records Management System 1.0 via the specialization parameter in doctors.php

CVE-2021-41598: Release notes - GitHub Docs

A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but if the user later updated the set of repositories the app was installed on after the GitHub App had configured additional user-level permissions, those additional permissions would not be displayed, leading to more permissions being granted than the user potentially intended. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program.