Istio -- Security vulnerabilities

Istio reports: Two security vulnerabilities have recently been identified in the Envoy proxy. The vulnerabilities are centered on the fact that Envoy did not normalize HTTP URI paths and did not fully validate HTTP/1.1 header values. These vulnerabilities impact Istio features that rely on Envoy ...

Envoy Passport Information Disclosure Vulnerability (CNVD-2019-08355)

Envoy Passport is a visitor management application. An information disclosure vulnerability exists in Envoy Passport versions 2.2.5 iPhone and 2.4.0 Android. A local attacker can exploit this vulnerability to gain access to sensitive information...

Envoy Passport Information Disclosure Vulnerability

Envoy Passport is a visitor management application. An information disclosure vulnerability exists in Envoy Passport versions 2.2.5 iPhone and 2.4.0 Android. A local attacker can exploit this vulnerability to gain access to sensitive information...

CVE-2018-17500

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of hardcoded OAuth Creds in plaintext. An attacker could exploit this vulnerability to obtain sensitive information...

CVE-2018-17499

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of unencrypted data in logs. An attacker could exploit this vulnerability to obtain two API keys, a token and other sensitive information...

CVE-2018-17499

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of unencrypted data in logs. An attacker could exploit this vulnerability to obtain two API keys, a token and other sensitive information...

Hardcoded credentials

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of hardcoded OAuth Creds in plaintext. An attacker could exploit this vulnerability to obtain sensitive information...

Information disclosure

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of unencrypted data in logs. An attacker could exploit this vulnerability to obtain two API keys, a token and other sensitive information...

CVE-2018-17500

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of hardcoded OAuth Creds in plaintext. An attacker could exploit this vulnerability to obtain sensitive information...

CVE-2018-17500

CVE-2018-17500 details (from provided documents) : Envoy Passport for Android and Envoy Passport for iPhone store hardcoded OAuth credentials in plaintext, enabling a local attacker to obtain sensitive information. The vulnerability is triggered by insecure storage of credentials in the applicati...

CVE-2018-17499

CVE-2018-17499 affects Envoy Passport for Android and Envoy Passport for iPhone. Connected CNVD-2019-08356 confirms an information-disclosure vulnerability caused by storing unencrypted data in logs, enabling a local attacker to access sensitive information such as two API keys and a token. Affec...

CVE-2018-17499

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of unencrypted data in logs. An attacker could exploit this vulnerability to obtain two API keys, a token and other sensitive information...

CVE-2018-17499: Cleartext Storage of Sensitive Information

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of unencrypted data in logs. An attacker could exploit this vulnerability to obtain two API keys, a token and other sensitive information...

CVE-2018-17500: Insufficiently Protected Credentials

Envoy Passport for Android and Envoy Passport for iPhone could allow a local attacker to obtain sensitive information, caused by the storing of hardcoded OAuth Creds in plaintext. An attacker could exploit this vulnerability to obtain sensitive information...

PT-2019-9498

Name of the Vulnerable Software and Affected Versions Envoy Passport for Android affected versions not specified Envoy Passport for iPhone affected versions not specified Description The issue is caused by the storage of hardcoded OAuth credentials in plaintext, allowing a local attacker to obtai...

PT-2019-9497

Name of the Vulnerable Software and Affected Versions Envoy Passport for Android affected versions not specified Envoy Passport for iPhone affected versions not specified Description The issue allows a local attacker to obtain sensitive information due to the storage of unencrypted data in logs...

Visitor Kiosk Access Systems Riddled with Bugs

Visitor-management systems protect business against physical threats such as unwanted and unidentified guests. But many of these lobby-based perimeter checkpoints are opening up companies to a bevy of cyber-threats. On Monday, IBM’s penetration testing team, X-Force Red, released a report that...

envoy/config_fuzz_test: Heap-use-after-free in std::__1::__bucket_list_deallocator<std::__1::allocator<std::__1::__hash_node_ba

Project: https://github.com/envoyproxy/envoy.git Detailed report: https://oss-fuzz.com/testcase?key=5666128418832384 Project: envoy Fuzzer: libFuzzerenvoyconfigfuzztest Fuzz target binary: configfuzztest Job Type: libfuzzerasanenvoy Platform Id: linux Crash Type: Heap-use-after-free READ 8 Crash...

envoy/config_fuzz_test: Heap-use-after-free in Envoy::Server::InitManagerImpl::initializeTarget

Project: https://github.com/envoyproxy/envoy.git Detailed report: https://oss-fuzz.com/testcase?key=5664687524413440 Project: envoy Fuzzer: libFuzzerenvoyconfigfuzztest Fuzz target binary: configfuzztest Job Type: libfuzzerasanenvoy Platform Id: linux Crash Type: Heap-use-after-free READ 8 Crash...

WS-2019-0519

In Envoy v1.9.0 and v1.9.1, it was possible to have two filter chains that didn't have proto equivalent FilterChainMatches, yet had semantically equivalent matchers. E.g. when one filter chain has a not-yet-implemented field. This led to a situation where the first filter chain might register for...