CVE-2024-0009

SC-7 enforces monitoring and control at external and key internal interfaces, preventing channels from unverified sources via boundary rules.

Authentication of users/services/hardware directly enforces source verification for communication channels.

Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.

Network protections reduce unauthorized channel usage but do not specifically require origin verification at channel setup.

Network security controls enforce source verification and channel authentication for incoming communications.

Security of network services includes validating the origin of service requests and connections.

A.8.24 mandates proper use of cryptography (algorithms, key management, protection of data in transit/storage) but has no bearing on whether a product correctly verifies the origin of an incoming communication channel; the weakness can still be present and exploited regardless of cryptographic controls.

A.8.26 requires identifying and specifying requirements for resilience against malicious attacks (explicitly naming SQL injection) plus input validation, authentication, segregation of access, output controls, and cryptography; these can address origin verification for expected channels in some (but not all) application designs, leaving a bounded remainder where the weakness is still exploitable.

A.8.27 mandates security-by-design principles (defense-in-depth, least privilege, assume-breach, distrust-external-input, zero-trust verification) plus design reviews that can catch and block origin-validation gaps in many common cases, but leaves a bounded remainder (e.g. protocol-level or third-party component origin errors not surfaced by the organization's review process).

Secure coding practices can prevent improper source verification if explicitly required.