LiveActive security incident?Get immediate response
CVE Record

CVE-2016-15011: e-Contract dssp SignResponseVerifier.java checkSignResponse xml external entity reference

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 upgrade the affected component. The identifier VDB-217549 was assigned to this vulnerability.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2016-15011 affects e-Contract dssp versions 1.3.0 and 1.3.1. A flawed XML handling path in signature response verification can allow XML external entity behavior, creating limited confidentiality, integrity, and availability risk. The named fix is upgrading to dssp 1.3.2.

Executive priority

Schedule remediation in the normal vulnerability cycle, faster for externally connected or partner-facing DSSP workflows. The issue has a clear upgrade path and moderate technical impact, but no provided evidence of active exploitation.

Technical view

The issue is CWE-611 in checkSignResponse within SignResponseVerifier.java. The source bundle says crafted manipulation can trigger XML external entity reference handling. CVSS 3.1 is 5.5 with adjacent attack vector, low complexity, low privileges, no user interaction, and low CIA impact.

Likely exposure

Exposure is limited to systems that embed or depend on e-Contract dssp 1.3.0 or 1.3.1 and process DSSP SignResponse XML. The bundle does not identify other affected products or deployment patterns.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. VulDB assigns VDB-217549 and the CVSS vector requires adjacent access and low privileges. Treat exploit status as unconfirmed, not actively exploited.

Researcher notes

Evidence is specific but narrow: affected versions, vulnerable file/function, CWE-611, CVSS vector, and patch identifiers are provided. The bundle does not provide exploit details, environmental prerequisites beyond CVSS, or proof of exploitation.

Mitigation direction

  • Upgrade affected e-Contract dssp deployments to version 1.3.2.
  • Confirm the ec423834 patch is included in deployed builds.
  • Review vendor release notes before relying on compensating controls.
  • Prioritize systems that process untrusted or partner-supplied SignResponse XML.

Validation and detection

  • Search SBOMs and dependency manifests for e-Contract dssp versions 1.3.0 or 1.3.1.
  • Verify production artifacts report dssp 1.3.2 after remediation.
  • Review code paths that call checkSignResponse or process DSSP SignResponse XML.
  • Confirm vulnerability scanners map findings to CVE-2016-15011 or VDB-217549.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-611: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-15011 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2016-15011Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
e-Contractdssp1.3.0, 1.3.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.