Skip to content
OpenAdvisories

Weakness (CWE)

CWE-669: Incorrect Resource Transfer Between Spheres

Class Draft

The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.

Source: MITRE CWE-669

95 results · Feed

  • Critical 9.1

    An issue was discovered in the Shannon RCS component in Samsung Exynos Modem 5123 and 5300. Incorrect resource transfer…

  • High 7.5

    An issue was discovered in the Shannon RCS component in Samsung Exynos Modem 5123 and 5300. Incorrect resource transfer…

  • Medium 6.5

    An issue was discovered in TigerGraph Enterprise Free Edition 3.x. Data loading jobs in gsql_server, created by any use…

  • High 7.2

    Elrond go Processing: fallback search of SCRs when not found in the main cache

    Elrond-GO is a go implementation for the Elrond Network protocol. Versions prior to 1.3.50 are subject to a processing issue where nodes are affected when trying to process a cross-shard relayed transaction with a smart contract deploy transaction data. The p…

  • Medium 4.3

    Parse Server subject to Incorrect Resource Transfer Between Spheres

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 4.10.15, or 5.0.0 and above prior to 5.2.6, a user can write to the session object of another user if the session object ID is known. …

  • Medium 5.3

    Cross chain utilities for Arbitrum L2 see EOA calls as cross chain calls

    OpenZeppelin Contracts is a library for secure smart contract development. Contracts using the cross chain utilities for Arbitrum L2, `CrossChainEnabledArbitrumL2` or `LibArbitrumL2`, will classify direct interactions of externally owned accounts (EOAs) as cr…

  • High 8.2

    A CWE-669: Incorrect Resource Transfer Between Spheres vulnerability exists that could allow unauthorized access when a…

  • Unscored —

    A CWE-669: Incorrect Resource Transfer Between Spheres vulnerability exists that could cause data exfiltration and unau…

  • Medium 6.5

    Publify - Improper Authorization Leads to Guest Signup Restriction Bypass

    In Publify, 9.0.0.pre1 to 9.2.4 are vulnerable to Improper Access Control. “guest” role users can self-register even when the admin does not allow. This happens due to front-end restriction only.

  • Medium 4.3

    Password policy evasion in products of MB connect line and Helmholz

    In MB connect line mymbCONNECT24, mbCONNECT24 and Helmholz myREX24 and myREX24.virtual in all versions through v2.11.2 an authenticated attacker can change the password of his account into a new password that violates the password policy by intercepting and m…

  • Medium 5.2
    CVE-2020-15257 Public exploit

    containerd-shim API Exposed to Host Network Containers

    containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s AP…

  • Medium 5.9

    Incorrect Resource Transfer Between Spheres in eclipse-wtp

    In all versions prior to version 3.9.6 for eclipse-wtp, all versions prior to version 9.4.4 for eclipse-cdt, and all versions prior to version 3.0.1 for eclipse-groovy, Spotless was resolving dependencies over an insecure channel (http). If the build occurred…

  • High 8.1

    Incorrect Resource Transfer Between Spheres in Grails

    Grails before 3.3.10 used cleartext HTTP to resolve the SDKMan notification service. NOTE: users' apps were not resolving dependencies over cleartext HTTP.

  • High 8.1

    Eclipse Vorto resolved Maven build artifacts for the Xtext project over HTTP instead of HTTPS

    Eclipse Vorto versions prior to 0.11 resolved Maven build artifacts for the Xtext project over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by a MITM attack. Hence produced build artifacts of Vorto might be i…

  • Medium 5.7

    Incorrect messages from Juniper Identity Management Service (JIMS) can trigger Denial of Service or firewall bypass conditions for SRX series devices

    Juniper Identity Management Service (JIMS) for Windows versions prior to 1.1.4 may send an incorrect message to associated SRX services gateways. This may allow an attacker with physical access to an existing domain connected Windows system to bypass SRX fire…