CVE-2016-15011: A vulnerability classified as problematic was found in e-Contract dssp up to 1.3.1

Q: How do I fix CVE-2016-15011?

dssp: upgrade to 1.3.2. Exact commands for each OS are on this page.

Q: Is CVE-2016-15011 being exploited?

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

Q: What does CVE-2016-15011 affect?

CVE-2016-15011 affects dssp. Severity is medium (CVSS 5.5). A vulnerability classified as problematic was found in e-Contract dssp up to 1.3.1. Affected by this vulnerability is the function checkSignResponse of the file dssp-client/src/main/java/be/e_contract/dssp/client/SignResponseVerifier.java.

Q: How urgent is CVE-2016-15011?

Priority 33/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2016-15011 is a medium-severity flaw (CVSS 5.5) affecting dssp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as problematic was found in e-Contract dssp up to 1.3.1. Affected by this vulnerability is the function checkSignResponse of the file dssp-client/src/main/java/be/e_contract/dssp/client/SignResponseVerifier.java. The manipulation leads to xml external entity reference. Upgrading to version 1.3.2 is able to address this issue. The identifier of the patch is ec4238349691ec66dd30b416ec6eaab02d722302. It is recommended to u

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Weakness	CWE-611
Published	2023-01-06
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: e-contract

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

Am I affected?

Timeline

2023-01-06 10:15 UTCPublished CVE record published
2026-06-17 00:40 UTCUpdated Record last modified

e-contract dssp UPGRADE

Affected: < 1.3.2

Fixed in: 1.3.2

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 1.3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dssp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dssp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2016-15011?

dssp: upgrade to 1.3.2. Exact commands for each OS are on this page.

Is CVE-2016-15011 being exploited?

CVE-2016-15011 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-2016-15011 affect?

CVE-2016-15011 affects dssp. Severity is medium (CVSS 5.5). A vulnerability classified as problematic was found in e-Contract dssp up to 1.3.1. Affected by this vulnerability is the function checkSignResponse of the file dssp-client/src/main/java/be/e_contract/dssp/client/SignResponseVerifier.java.

How urgent is CVE-2016-15011?

Priority 33/100. No elevated risk signals yet.

Software pages

Java vulnerabilities

References

← Back to latest CVEs