Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27491PUBLISHED: 2021-07-30Ypsomed mylife Cloud, mylife Mobile Application:Ypsomed mylife Cloud,All versions prior to 1.7.2,Ypsomed mylife App,All versions prior to 1.7.5,The Ypsomed mylife Cloud discloses password hashes during the registration process.
CVE-2021-27495PUBLISHED: 2021-07-30Ypsomed mylife Cloud, mylife Mobile Application:Ypsomed mylife Cloud,All versions prior to 1.7.2,Ypsomed mylife App,All versions prior to 1.7.5,he Ypsomed mylife Cloud reflects the user password during the login process after redirecting the user from a HTTPS endpoint to a HTTP endpoint.
CVE-2021-32807PUBLISHED: 2021-07-30
The module `AccessControl` defines security policies for Python code used in restricted code within Zope applications. Restricted code is any code that resides in Zope's object database, such as the contents of `Script (Python)` objects. The policies defined in `AccessControl` severely restrict acce...
CVE-2021-22521PUBLISHED: 2021-07-30A privileged escalation vulnerability has been identified in Micro Focus ZENworks Configuration Management, affecting version 2020 Update 1 and all prior versions. The vulnerability could be exploited to gain unauthorized system privileges.
CVE-2021-34629PUBLISHED: 2021-07-30The SendGrid WordPress plugin is vulnerable to authorization bypass via the get_ajax_statistics function found in the ~/lib/class-sendgrid-statistics.php file which allows authenticated users to export statistic for a WordPress multi-site main site, in versions up to and including 1.11.8.
The State of Cybersecurity Incident ResponseIn this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Incident Readiness and Building Response Playbook
In this special report, learn the Xs and Os of any good security incident readiness and response playbook.
Tweet This
0 Comments
User Rank: Strategist
3/4/2019 | 5:34:35 PM
In general, providing an input with an apostrophe should be considered valid, even if the backend uses this value in an SQL query (as the real data being search may have such values, e.g. Name: O'Neill). If I include the text "<grin>" with-in some online forum post/comment, it shouldn't be rejected/removed for no-HTML input fields, but be treated as verbatuim text that is properly escaped in output HTML.
Input validation should normally only be done for specific business logic (e.g. usernames are limited to ASCII letters/numbers and must start with a letter), or general sanity checks (e.g. only ASCII; only valid UTF-8 encoded strings; doesn't contain invalid UNICODE composed sequences; no embedded NUL characters [when using length specified strings]).