Security readout for executives and security teams
GraniteDS AMF3 deserialization can let an attacker influence which Java classes are created and which setters run. In the wrong application classpath, that can become remote code execution. Business urgency depends on whether exposed applications still use GraniteDS 3.1.1.G/GA endpoints that accept untrusted AMF data. Likely exposure is limited to Java applications using GraniteDS Framework 3.1.1.G/GA with AMF3 endpoints reachable by untrusted users. Systems without GraniteDS, without exposed AMF deserialization, or without useful classpath classes have lower practical exposure. Prioritize internet-facing or partner-facing Java applications first. Treat confirmed exposed GraniteDS AMF endpoints as high risk because successful exploitation may lead to code execution, but avoid emergency assumptions without confirming product presence and reachability. Mitigation focus: Inventory applications for GraniteDS Framework 3.1.1.G or 3.1.1.GA usage.; Restrict AMF endpoints to authenticated and trusted clients where business functionality permits.; Check GraniteDS and CERT guidance for fixed versions or vendor-recommended workarounds..
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.
CWE-913: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-3200 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://codewhitesec.blogspot.com/2017/04/amf.htmlCVE reference · x_refsource_MISC
- VU#307983CVE reference · third-party-advisory, x_refsource_CERT-VN
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.
Improper Control of Dynamically-Managed Code Resources
Improper Control of Dynamically-Managed Code Resources represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.