aedart support up to 0.6.0 meta MetadataRecord prototype pollution

Summaryinfo

A vulnerability classified as problematic has been found in aedart support up to 0.6.0. This issue affects the function meta. This manipulation of the argument MetadataRecord causes prototype pollution. This vulnerability is tracked as CVE-2023-30857. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in aedart support up to 0.6.0. Affected by this vulnerability is the function meta. The manipulation of the argument MetadataRecord with an unknown input leads to a prototype pollution vulnerability. The CWE definition for the vulnerability is CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. As an impact it is known to affect integrity. The summary by CVE is:

@aedart/support is the support package for Ion, a monorepo for JavaScript/TypeScript packages. Prior to version `0.6.1`, there is a possible prototype pollution issue for the `MetadataRecord`, when merged with a base class' metadata object, in `meta` decorator from the `@aedart/support` package. The likelihood of exploitation is questionable, given that a class's metadata can only be set or altered when the class is decorated via `meta()`. Furthermore, object(s) of sensitive nature would have to be stored as metadata, before this can lead to a security impact. The issue has been patched in version `0.6.1`.

The weakness was disclosed 04/29/2023 as GHSA-wwxh-74fx-33c6. The advisory is shared at github.com. This vulnerability is known as CVE-2023-30857 since 04/18/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.

Upgrading to version 0.6.1 eliminates this vulnerability. Applying the patch c3e2ee08710d4164d796ecb66ed291335dae9291 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• aedart

Name

• support

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6.0

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion