Update dependency org.liquibase:liquibase-core to v4.11.0 #4287
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
SQL InjectionClick here to find a SQL Injection training lab DescriptionA SQL Injection is not a new or overly complicated type of attack, yet it continues to sit atop the OWASP Top Ten Application Security Risks after more than 20 years of it having been publicly utilized. This is primarily due to its inherent relative ease of use, coupled with its severity of impact when directed toward the staggeringly high number of websites with poorly written, vulnerable code. SQL is a query language that is designed to access, modify, and delete data stored in relational databases. Numerous web applications and websites use SQL databases as their method of data storage. Applications with a higher prevalence of older functional interfaces such as PHP and ASP are relatively more susceptible to SQL Injection flaws than applications based on more recent technologies. Applications are vulnerable to attacks when user-supplied data is not validated, filtered for escape characters or sanitized by the application. An attacker can use SQL Injection to manipulate an SQL query via the input data from the client to the application, thus forcing the SQL server to execute an unintended operation constructed using untrusted input. Read moreImpactA successful SQL Injection attack can result in a malicious user gaining complete access to all data in a database server with the ability to execute unauthorized SQL queries and compromise the confidentiality, integrity, and availability of the application. Depending on the backend DBMS used and the permissions granted to the user on the database, a SQL Injection could result in arbitrary file read/write and even remote code execution. The severity of attacks that have leveraged SQL Injection should not be understated. Notorious breaches, including the devastating and internationally renowned hacks of Sony Pictures and LinkedIn, for example, are reported to have been executed using SQL Injection. ScenariosSubverting application logic through SQL can lead to unpredictable outcomes depending on the context of the SQL statement the strategy of the attacker. There are well-known exploitation techniques that attackers leverage depending on the vulnerability within the implementation of the code:
It is called blind SQL Injection when the injection succeeds, but the code doesn't return the result of the manipulated query to the attacker. Blind injections are still exploitable to retrieve the content using timing analysis, content analysis, or other out-of-bound techniques. The following is a classic example of subverting application logic to bypass access controls. Usernames and passwords are ubiquitous as the method for logging into applications. In this benign scenario, a user submits the username SELECT * FROM users WHERE username = 'user' AND password = 'secret'The login is successful if the query returns the details of the user. If the query doesn't return the user details, it is rejected. By leveraging single quotes and SQL comments ( The following example illustrates this in action. By entering SELECT * FROM users WHERE username = 'administrator'--' AND password = 'The database evaluates this statement without the commented out part, executing just the first part: SELECT * FROM users WHERE username = 'administrator'Since the manipulated query always returns the details of the PreventionTo avoid SQL Injection vulnerabilities, developers need to use parameterized queries, specifying placeholders for parameters so that they are not considered as a part of the SQL command; rather, as solely data by the database. When working with legacy systems, developers need to escape inputs before adding them to the query. Object Relational Mappers (ORMs) make this easier for the developer; however, they are not a panacea, with the underlying mitigations still entirely relevant: untrusted data needs to be validated, query concatenation should be avoided unless absolutely necessary, and minimizing unnecessary SQL account privileges is crucial. TestingVerify that where parameterized or safer mechanisms are not present, context-specific output encoding is used to protect against injection attacks, such as the use of SQL escaping to protect against SQL Injection.
|
Micro-Learning Topic: SQL injection (Detected by phrase)Matched on "SQLi"This is probably one of the two most exploited vulnerabilities in web applications and has led to a number of high profile company breaches. It occurs when an application fails to sanitize or validate input before using it to dynamically construct a statement. An attacker that exploits this vulnerability will be able to gain access to the underlying database and view or modify data without permission. Try this challenge in Secure Code Warrior |
Micro-Learning Topic: Injection attack (Detected by phrase)Matched on "Injection attack"Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization. Source: https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project Try this challenge in Secure Code Warrior |
This PR contains the following updates:
4.10.0->4.11.0Release Notes
liquibase/liquibase
v4.11.0Compare Source
Liquibase 4.11 release
Please report any issues to https://github.com/liquibase/liquibase/issues.
Breaking Changes
Starting with 4.11, we moved the global libraries we ship with the CLI from the
libdirectory to a newinternaldirectory structure. Thelibdirectory is still included in the classpath as the place users can add whatever additional global drivers/libraries they need.The
liquibase --versionoutput has been enhanced to also include the 3rd party libraries being used and their versions.Impacts:
libandinternal/lib. You should manually delete any files inlibwhich you did not add yourself. Liquibase will continue to work even with the duplicate libraries, but you may not be running the latest version of ones we ship, since thelibfiles take priority over what is ininternal/lib. New installs are not impacted by this.libyou will need to update it to reflect the newinternal/liblocationFor security reasons, we have also changed what is logged by the CLI to only log
liquibasechannel messages by default, rather than all log channels. If you are relying on logging from non-Liquibase libraries, you can add channels with the new--log-channelsflag, including--log-channels=allto restore the old functionality.Enhancements
liband into a newinternal/libdirectory by @nvoxland in https://github.com/liquibase/liquibase/pull/2850--monitor-performanceargument for the CLI (and only the CLI) which enables profiling of the Liquibase run. The generated profiling information can help us understand and fix performance issues easier. https://github.com/liquibase/liquibase/pull/2599Fixes
(0)::realby @nvoxland in https://github.com/liquibase/liquibase/pull/2836Updates
Security Updates
JDBC Driver and Third-Party Library Updates
OWASP Dependency Check: Reported Vulnerabilities
New Contributors
Full Changelog: liquibase/liquibase@v4.10.0...v4.11.0
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.