Existing vulnerability analysis

# Why?

Java, being the most popular software platform out there is a target of everlasting and rigorous security research.
Such research creates a lot of CVEs, and having a clear understanding of the implications of having vulnerable dependencies is something, we as developers owe server operators.

For the time being, I don't have sufficient competence to read vulnerability reports, but it seems like JDBC URLs wreaked havoc on dependencies other than log4j. Snyk reporter suggests that there are DoS and 2x RCEs in XMage dependencies as they stand.

# How

## Immediate actions (addressing RCEs)

- [ ] Perhaps, bump com.h2database:h2 to 2.1.210+
- [ ] Assess https://security.snyk.io/vuln/SNYK-JAVA-COMH2DATABASE-2348247
- [ ] Assess https://security.snyk.io/vuln/SNYK-JAVA-COMH2DATABASE-2331071
- [ ] If it is plausible that the vulnerabilities are exploitable, upgrade the dependency and make needed changes to the code to match incompatible APIs

## Future work (DoS)

- [ ] Perhaps, bump org.jboss.remoting:jboss-remoting to 5.0.23+
- [ ] Assess https://security.snyk.io/vuln/SNYK-JAVA-ORGJBOSSREMOTING-1300042
- [ ] If it is plausible that the vulnerabilities are exploitable, upgrade the dependency and make needed changes to the code to match incompatible APIs