Security readout for executives and security teams
Plain-English summary
This CVE describes a denial-of-service style condition where OpenDaylight's odl-mdsal-xsql component can trigger Java out-of-memory errors and sharply increased resource consumption. The record names tested OpenDaylight versions 3.3 and 4.0, but does not provide severity, CVSS, a patch, or confirmed exploitation.
Executive priority
Prioritize if OpenDaylight is business-critical or internet-adjacent. The issue affects availability, but urgency cannot be scored confidently from the available sources because severity, exploitability, and fixes are not specified.
Technical view
The public record identifies OpenDaylight odl-mdsal-xsql as vulnerable to excessive resource consumption leading to Java out-of-memory errors. Evidence is limited to tested versions 3.3 and 4.0 and a referenced Aalto thesis PDF. No CWE, CVSS vector, affected CPE, exploit status, or remediation details are provided.
Likely exposure
Exposure is most plausible where OpenDaylight 3.3 or 4.0 is deployed and the odl-mdsal-xsql component is installed or enabled. The supplied sources do not identify other affected versions or products.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, public exploit availability, or exploitation prerequisites. Treat this as an availability risk until vendor or project guidance clarifies scope and fixed versions.
Researcher notes
The record is sparse: component and tested versions are named, but affected CPEs are n/a and no CVSS or CWE is present. Validate the original PDF and OpenDaylight advisories before broad version conclusions.
Mitigation direction
- Inventory OpenDaylight deployments for versions 3.3 and 4.0.
- Check whether odl-mdsal-xsql is installed or enabled.
- Review OpenDaylight project guidance for fixed versions or configuration mitigations.
- Limit component exposure according to existing network access controls.
- Monitor Java heap, process restarts, and resource exhaustion alerts.
Validation and detection
- Confirm OpenDaylight version and installed feature set on each deployment.
- Identify systems running or loading odl-mdsal-xsql.
- Review historical logs for Java out-of-memory errors.
- Check monitoring for unusual CPU, memory, or restart patterns.
- Document whether vendor guidance names a fixed release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2017-1000359 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://aaltodoc.aalto.fi/bitstream/handle/123456789/21584/master_Bidaj_Andi_2016.pdfCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
