Approved changes feed: RSS · Atom

cpe:2.3:a:oracle:secure_global_desktop:5.4:*:*:*:*:*:*:*

part: a version: 5.4 update: *

VendorOracle (3509f9eb-d8a0-57da-b153-b8021021b133)
ProductSecure Global Desktop (7151b345-8c8a-56d3-8ea6-b075f9193b11)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2019-3823 vulnerable 2026-06-08 05:13:56.128872 Details available
MEDIUM (4.3)
libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to `smtp_endofresp()` isn't NUL terminated and contains no character ending the parsed number, and `len` is set to 5, then the `strtol()` call reads beyond the allocated buffer. The read contents will not be returned to the caller.
Published: 2019-02-06T20:00:00.000Z
Updated: 2026-04-15T20:52:15.885Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-3822 vulnerable 2026-06-08 05:13:56.125058 Details available
HIGH (7.1)
libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (`lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()`), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.
Published: 2019-02-06T20:00:00.000Z
Updated: 2026-04-15T20:52:52.914Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-1559 vulnerable 2026-06-08 05:13:26.161342 0-byte record padding oracle
If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q).
Published: 2019-02-27T23:00:00.000Z
Updated: 2024-09-17T04:20:35.057Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-17091 vulnerable 2026-06-08 05:13:09.908625 Details available
faces/context/PartialViewContextImpl.java in Eclipse Mojarra, as used in Mojarra for Eclipse EE4J before 2.3.10 and Mojarra JavaServer Faces before 2.2.20, allows Reflected XSS because a client window field is mishandled.
Published: 2019-10-02T13:58:49.000Z
Updated: 2024-08-05T01:33:16.741Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-10092 vulnerable 2026-06-08 05:12:22.230883 Details available
In Apache HTTP Server 2.4.0-2.4.39, a limited cross-site scripting issue was reported affecting the mod_proxy error page. An attacker could cause the link on the error page to be malformed and instead point to a page of their choice. This would only be exploitable where a server was set up with proxying enabled but was misconfigured in such a way that the Proxy Error page was displayed.
Published: 2019-09-26T14:07:46.000Z
Updated: 2024-08-04T22:10:09.500Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2019-0227 vulnerable 2026-06-08 05:12:19.440176 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-8032 vulnerable 2026-06-08 05:12:05.076069 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-1304 vulnerable 2026-06-08 05:11:17.607450 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-16890 vulnerable 2026-06-08 05:11:05.748056 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-11784 vulnerable 2026-06-08 05:10:39.021324 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-11763 vulnerable 2026-06-08 05:10:38.927518 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-0735 vulnerable 2026-06-08 05:10:24.643216 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.