Philips Vue PACS
A third-party product component writes data past the end, or before the beginning, of the intended buffer. A third-party product component deserializes untrusted data without sufficiently verifying that the resulting data will be valid. A third-party product component deserializes untrusted data without sufficiently verifying that the resulting data will be valid. A third-party product component deserializes untrusted data without sufficiently verifying that the resulting data will be valid. A third-party product component deserializes untrusted data without sufficiently verifying that the resulting data will be valid. A third-party product component deserializes untrusted data without sufficiently verifying that the resulting data will be valid. A third-party product component deserializes untrusted data without sufficiently verifying that the resulting data will be valid. A third-party product component deserializes untrusted data without sufficiently verifying that the resulting data will be valid. A third-party product component does not properly control the allocation and maintenance of CPU use upon receiving a large invalid packet frame. Philips Vue PACS does not properly assign, modify, track, or check actor privileges, creating an unintended sphere of control for that actor. Philips Vue PACS uses default credentials for potentially critical functionality. Philips Vue PACS does not require that users have strong passwords, which could make it easier for attackers to compromise user accounts. A validated user not explicitly authorized to have access to certain sensitive information could access Philips Vue PACS on the same network to expose that information.