CVE-2018-14925: Matera Banco 1.0.0 mishandles Java errors in the backend, as demonstrated by a stack trace revealing use of ne

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2018-14925 is a critical-severity flaw (CVSS 9.8) affecting banco. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Matera Banco 1.0.0 mishandles Java errors in the backend, as demonstrated by a stack trace revealing use of net.sf.acegisecurity components.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 25%)
CISA exploited list	No
Weakness	CWE-209
Published	2018-08-03
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: matera

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-08-03 21:29 UTCPublished CVE record published
2026-06-17 01:41 UTCUpdated Record last modified

matera banco DOWNGRADE

Affected: 1.0.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy banco || rpm -q banco || banco --version

2. No fixed release: DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison banco sudo apt install banco=<VERSION_BEFORE_1.0.0> sudo apt-mark hold banco

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list banco sudo dnf downgrade banco-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add banco

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-14925?

banco: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-14925 being exploited?

CVE-2018-14925 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-14925 affect?

CVE-2018-14925 affects banco. Severity is critical (CVSS 9.8). Matera Banco 1.0.0 mishandles Java errors in the backend, as demonstrated by a stack trace revealing use of net.sf.acegisecurity components.

How urgent is CVE-2018-14925?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

CVE-2018-14929 MEDIUM 6.1 DOWNGRADE Matera Banco 1.0.0 is vulnerable to multiple reflected XSS, as demonstrated by the /contingency/web/index.jsp
CVE-2018-14928 HIGH 7.5 DOWNGRADE /contingency/servlet/ServletFileDownload executes as root and provides unauthenticated access to files via the
CVE-2018-14927 MEDIUM 5.3 DOWNGRADE Matera Banco 1.0.0 is vulnerable to path traversal (allowing access to system files outside the default applic
CVE-2018-14926 HIGH 8.8 DOWNGRADE Matera Banco 1.0.0 allows CSRF, as demonstrated by a /contingency/web/messageSend/messageSendHandler.jsp reque
CVE-2018-14924 MEDIUM 6.1 DOWNGRADE Matera Banco 1.0.0 is vulnerable to multiple stored XSS, as demonstrated by the sca/privilegio/consultarUsuari

References

← Back to latest CVEs