|
Il Thesaurus offre una rappresentazione della conoscenza di un insieme di termini relativi alla Cybersecurity,... |
Il servizio mostra una rappresentazione 3D del traffico di rete relativo ad attacchi ad una honeypot a Pisa. Inoltre,... |
Il servizio offre la possibilità di cercare informazioni, note pubblicamente, relative a vulnerabilità di sicurezza... |
Il servizio si prefigge di individuare comportamenti tipici dei ransomware quali, ad esempio, la cifratura di una... |
| Published | Description | |
|---|---|---|
| CVE-2020-26250 |
01-12-2020 21:15:00 |
OAuthenticator is an OAuth login mechanism for JupyterHub. In oauthenticator from version 0.12.0 and before 0.12.2, the deprecated (in jupyterhub 1.2) configuration `Authenticator.whitelist`, which should be transparently mapped to `Authenticator.allowed_users` with a warning, is instead ignored by OAuthenticator classes, resulting in the same behavior as if this configuration has not been set. If this is the only mechanism of authorization restriction (i.e. no group or team restrictions in configuration) then all authenticated users will be allowed. Provider-based restrictions, including deprecated values such as `GitHubOAuthenticator.org_whitelist` are **not** affected. All users of OAuthenticator 0.12.0 and 0.12.1 with JupyterHub 1.2 (JupyterHub Helm chart 0.10.0-0.10.5) who use the `admin.whitelist.users` configuration in the jupyterhub helm chart or the `c.Authenticator.whitelist` configuration directly. Users of other deprecated configuration, e.g. `c.GitHubOAuthenticator.team_whitelist` are **not** affected. If you see a log line like this and expect a specific list of allowed usernames: "[I 2020-11-27 16:51:54.528 JupyterHub app:1717] Not using allowed_users. Any authenticated user will be allowed." you are likely affected. Updating oauthenticator to 0.12.2 is recommended. A workaround is to replace the deprecated `c.Authenticator.whitelist = ...` with `c.Authenticator.allowed_users = ...`. If any users have been authorized during this time who should not have been, they must be deleted via the API or admin interface, per the referenced documentation. |
| CVE-2020-28575 |
01-12-2020 19:15:00 |
A heap-based buffer overflow privilege escalation vulnerability in Trend Micro ServerProtect for Linux 3.0 may allow an attacker to escalate privileges on affected installations. An attacker must first obtain the ability to execute high-privileged code on the target in order to exploit this vulnerability. |
| CVE-2020-28576 |
01-12-2020 19:15:00 |
An improper access control information disclosure vulnerability in Trend Micro Apex One and OfficeScan XG SP1 could allow an unauthenticated user to connect to the product server and reveal version and build information. |
| CVE-2020-28582 |
01-12-2020 19:15:00 |
An improper access control information disclosure vulnerability in Trend Micro Apex One and OfficeScan XG SP1 could allow an unauthenticated user to connect to the product server and reveal number of managed agents. |
| CVE-2020-28583 |
01-12-2020 19:15:00 |
An improper access control information disclosure vulnerability in Trend Micro Apex One and OfficeScan XG SP1 could allow an unauthenticated user to connect to the product server and reveal version, build and patch information. |
| Date | Title | Platform | Author |
|---|---|---|---|
|
01-12-2020 |
TypeSetter 5.1 - CSRF (Change admin e-mail) | php | Alperen Ergel |
|
01-12-2020 |
10-Strike Network Inventory Explorer 8.65 - Buffer Overflow (SEH) | windows | Sectechs |
|
01-12-2020 |
EPSON Status Monitor 3 'EPSON_PM_RPCV4_06' - Unquoted Service Path | windows | SamAlucard |
|
01-12-2020 |
Joomla! Component GMapFP 3.5 - Unauthenticated Arbitrary File Upload | php | ThelastVvV |
|
01-12-2020 |
Tailor Management System 1.0 - Unrestricted File Upload to Remote Code Execution | php | Saeed Bala Ahmed |
Italiano
English