LiveActive security incident?Get immediate response
CVE Record

CVE-2016-8744: Apache Brooklyn uses the SnakeYAML library for parsing YAML inputs.

Apache Brooklyn uses the SnakeYAML library for parsing YAML inputs. SnakeYAML allows the use of YAML tags to indicate that SnakeYAML should unmarshal data to a Java type. In the default configuration in Brooklyn before 0.10.0, SnakeYAML will allow unmarshalling to any Java type available on the classpath. This could provide an authenticated user with a means to cause the JVM running Brooklyn to load and run Java code without detection by Brooklyn. Such code would have the privileges of the Java process running Brooklyn, including the ability to open files and network connections, and execute system commands. There is known to be a proof-of-concept exploit using this vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Apache Brooklyn 0.9.0 and earlier could let an authenticated user submit YAML that causes the Brooklyn JVM to run Java code. That code could inherit the Brooklyn process privileges, including file, network, and command execution capabilities.

Executive priority

Treat as urgent where Apache Brooklyn is deployed. The business risk is authenticated takeover of the Brooklyn runtime, potentially affecting managed infrastructure and adjacent systems.

Technical view

Brooklyn used SnakeYAML to parse YAML inputs. In the default vulnerable configuration, SnakeYAML could deserialize YAML tags into any Java type available on the classpath, enabling authenticated code execution inside the Brooklyn JVM before version 0.10.0.

Likely exposure

Organizations are exposed if they run Apache Brooklyn 0.9.0 or earlier and allow authenticated users to provide YAML inputs to Brooklyn.

Exploitation context

The CVE record states a proof-of-concept exploit is known. The supplied sources do not show KEV listing or confirmed active exploitation.

Researcher notes

No CVSS or CWE data was supplied. Analysis relies on Apache and CVE descriptions: authenticated YAML deserialization through SnakeYAML, arbitrary class unmarshalling, JVM-level code execution, and known PoC existence.

Mitigation direction

  • Upgrade Apache Brooklyn deployments from 0.9.0 or earlier to 0.10.0 or later.
  • Restrict Brooklyn access to trusted authenticated users until upgraded.
  • Review vendor security guidance for any version-specific hardening details.
  • Audit Brooklyn process privileges and reduce unnecessary file, network, and command access.

Validation and detection

  • Inventory Apache Brooklyn versions across production, staging, and administrative systems.
  • Confirm whether authenticated users can submit YAML inputs to Brooklyn.
  • Review logs for unexpected Brooklyn JVM file, network, or child-process activity.
  • Verify upgraded systems no longer use the vulnerable default SnakeYAML behavior.
Prepared
Confidence
high
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2016-8744 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Brooklyn0.9.0 and all prior versionsListed
Weakness

CWE details

No CWE listed

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