Action not permitted
Modal body text goes here.
Modal Title
Modal Body
cve-2019-14241
Vulnerability from cvelistv5
Published
2019-07-23 12:02
Modified
2024-08-05 00:12
Severity ?
EPSS score ?
Summary
HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.
References
{ containers: { adp: [ { providerMetadata: { dateUpdated: "2024-08-05T00:12:43.367Z", orgId: "af854a3a-2127-422b-91ae-364da2661108", shortName: "CVE", }, references: [ { tags: [ "x_refsource_MISC", "x_transferred", ], url: "https://github.com/haproxy/haproxy/issues/181", }, { name: "109352", tags: [ "vdb-entry", "x_refsource_BID", "x_transferred", ], url: "http://www.securityfocus.com/bid/109352", }, { name: "openSUSE-SU-2019:2556", tags: [ "vendor-advisory", "x_refsource_SUSE", "x_transferred", ], url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html", }, { name: "openSUSE-SU-2019:2555", tags: [ "vendor-advisory", "x_refsource_SUSE", "x_transferred", ], url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html", }, ], title: "CVE Program Container", }, ], cna: { affected: [ { product: "n/a", vendor: "n/a", versions: [ { status: "affected", version: "n/a", }, ], }, ], descriptions: [ { lang: "en", value: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", }, ], problemTypes: [ { descriptions: [ { description: "n/a", lang: "en", type: "text", }, ], }, ], providerMetadata: { dateUpdated: "2019-11-24T00:07:07", orgId: "8254265b-2729-46b6-b9e3-3dfca2d5bfca", shortName: "mitre", }, references: [ { tags: [ "x_refsource_MISC", ], url: "https://github.com/haproxy/haproxy/issues/181", }, { name: "109352", tags: [ "vdb-entry", "x_refsource_BID", ], url: "http://www.securityfocus.com/bid/109352", }, { name: "openSUSE-SU-2019:2556", tags: [ "vendor-advisory", "x_refsource_SUSE", ], url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html", }, { name: "openSUSE-SU-2019:2555", tags: [ "vendor-advisory", "x_refsource_SUSE", ], url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html", }, ], x_legacyV4Record: { CVE_data_meta: { ASSIGNER: "cve@mitre.org", ID: "CVE-2019-14241", STATE: "PUBLIC", }, affects: { vendor: { vendor_data: [ { product: { product_data: [ { product_name: "n/a", version: { version_data: [ { version_value: "n/a", }, ], }, }, ], }, vendor_name: "n/a", }, ], }, }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "eng", value: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", }, ], }, problemtype: { problemtype_data: [ { description: [ { lang: "eng", value: "n/a", }, ], }, ], }, references: { reference_data: [ { name: "https://github.com/haproxy/haproxy/issues/181", refsource: "MISC", url: "https://github.com/haproxy/haproxy/issues/181", }, { name: "109352", refsource: "BID", url: "http://www.securityfocus.com/bid/109352", }, { name: "openSUSE-SU-2019:2556", refsource: "SUSE", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html", }, { name: "openSUSE-SU-2019:2555", refsource: "SUSE", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html", }, ], }, }, }, }, cveMetadata: { assignerOrgId: "8254265b-2729-46b6-b9e3-3dfca2d5bfca", assignerShortName: "mitre", cveId: "CVE-2019-14241", datePublished: "2019-07-23T12:02:36", dateReserved: "2019-07-23T00:00:00", dateUpdated: "2024-08-05T00:12:43.367Z", state: "PUBLISHED", }, dataType: "CVE_RECORD", dataVersion: "5.1", "vulnerability-lookup:meta": { nvd: "{\"cve\":{\"id\":\"CVE-2019-14241\",\"sourceIdentifier\":\"cve@mitre.org\",\"published\":\"2019-07-23T13:15:13.240\",\"lastModified\":\"2024-11-21T04:26:16.597\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.\"},{\"lang\":\"es\",\"value\":\"HAProxy hasta versión 2.0.2, permite a los atacantes causar una denegación de servicio (ha_panic) por medio de vectores relacionados con la función htx_manage_client_side_cookies en el archivo proto_htx.c.\"}],\"metrics\":{\"cvssMetricV30\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.0\",\"vectorString\":\"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:L/Au:N/C:N/I:N/A:P\",\"baseScore\":5.0,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"LOW\",\"authentication\":\"NONE\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"PARTIAL\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":10.0,\"impactScore\":2.9,\"acInsufInfo\":false,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-835\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"1.4\",\"versionEndIncluding\":\"1.9.8\",\"matchCriteriaId\":\"188F573A-5FCE-450C-95A3-53F567E1618B\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"2.0.0\",\"versionEndIncluding\":\"2.0.2\",\"matchCriteriaId\":\"C7F9D8D5-6D60-45C7-9E4D-3A49E5DE731D\"}]}]}],\"references\":[{\"url\":\"http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html\",\"source\":\"cve@mitre.org\"},{\"url\":\"http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html\",\"source\":\"cve@mitre.org\"},{\"url\":\"http://www.securityfocus.com/bid/109352\",\"source\":\"cve@mitre.org\",\"tags\":[\"Third Party Advisory\",\"VDB Entry\"]},{\"url\":\"https://github.com/haproxy/haproxy/issues/181\",\"source\":\"cve@mitre.org\",\"tags\":[\"Exploit\",\"Third Party Advisory\"]},{\"url\":\"http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"http://www.securityfocus.com/bid/109352\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Third Party Advisory\",\"VDB Entry\"]},{\"url\":\"https://github.com/haproxy/haproxy/issues/181\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Exploit\",\"Third Party Advisory\"]}]}}", }, }
suse-su-2019:3002-1
Vulnerability from csaf_suse
Published
2019-11-18 16:10
Modified
2019-11-18 16:10
Summary
Security update for haproxy
Notes
Title of the patch
Security update for haproxy
Description of the patch
This update for haproxy to version 2.0.5+git0.d905f49a fixes the following issues:
Security issue fixed:
- CVE-2019-14241: Fixed a cookie memory corruption problem. (bsc#1142529)
The update to 2.0.5 brings lots of features and bugfixes:
- new internal native HTTP representation called HTX, was already in 1.9 and is now enabled by default in 2.0
- end-to-end HTTP/2 support including trailers and continuation frames, as needed for gRPC ; HTTP/2 may also be upgraded from HTTP/1.1 using the H2 preface;
- server connection pooling and more advanced reuse, with ALPN protocol negotiation (already in 1.9)
- layer 7 retries, allowing to use 0-RTT and TCP Fast Open to the servers as well as on the frontend
- much more scalable multi-threading, which is even enabled by default on platforms where it was successfully tested ; by default, as many threads are started as the number of CPUs haproxy is allowed to run on. This removes a lot of configuration burden in VMs and containers
- automatic maxconn setting for the process and the frontends, directly based on the number of available FDs (easier configuration in containers and with systemd)
- logging to stdout for use in containers and systemd (already in 1.9). Logs can now provide micro-second resolution for some events
- peers now support SSL, declaration of multiple stick-tables directly in the peers section, and synchronization of server names, not just IDs
- In master-worker mode, the master process now exposes its own CLI and can communicate with all other processes (including the stopping ones), even allowing to connect to their CLI and check their state. It is also possible to start some sidecar programs and monitor them from the master, and the master can automatically kill old processes that survived too many reloads
- the incoming connections are load-balanced between all threads depending on their load to minimize the processing time and maximize the capacity (already in 1.9)
- the SPOE connection load-balancing was significantly improved in order to reduce high percentiles of SPOA response time (already in 1.9)
- the 'random' load balancing algorithm and a power-of-two-choices variant were introduced
- statistics improvements with per-thread counters for certain things, and a prometheus exporter for all our statistics;
- lots of debugging help, it's easier to produce a core dump, there are new commands on the CLI to control various things, there is a watchdog to fail cleanly when a thread deadlock or a spinning task are detected, so overall it should provide a better experience in field and less round trips between users and developers (hence less stress during an incident).
- all 3 device detection engines are now compatible with multi-threading and can be build-tested without any external dependencies
- 'do-resolve' http-request action to perform a DNS resolution on any, sample, and resolvers now support relying on /etc/resolv.conf to match the local resolver
- log sampling and balancing : it's now possible to send 1 log every 10 to a server, or to spread the logging load over multiple log servers;
- a new SPOA agent (spoa_server) allows to interface haproxy with Python and Lua programs
- support for Solaris' event ports (equivalent of kqueue or epoll) which will significantly improve the performance there when dealing with numerous connections
- some warnings are now reported for some deprecated options that will be removed in 2.1. Since 2.0 is long term supported, there's no emergency to convert them, however if you see these warnings, you need to understand that you're among their extremely rare users and just because of this you may be taking risks by keeping them
- A new SOCKS4 server-side layer was provided ; it allows outgoing connections to be forwarded through a SOCKS4 proxy (such as ssh -D).
- priority- and latency- aware server queues : it is possible now to assign priorities to certain requests and/or to give them a time bonus or penalty to refine control of the traffic and be able to engage on SLAs.
- internally the architecture was significantly redesigned to allow to further improve performance and make it easier to implement protocols that span over multiple layers (such as QUIC). This work started in 1.9 and will continue with 2.1.
- the I/O, applets and tasks now share the same multi-threaded scheduler, giving a much better responsiveness and fairness between all tasks as is visible with the CLI which always responds instantly even under extreme loads (started in 1.9)
- the internal buffers were redesigned to ease zero-copy operations, so that it is possible to sustain a high bandwidth even when forwarding HTTP/1 to/from HTTP/2 (already in 1.9)
Patchnames
SUSE-2019-3002,SUSE-SLE-Product-HA-15-2019-3002
Terms of use
CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
{ document: { aggregate_severity: { namespace: "https://www.suse.com/support/security/rating/", text: "moderate", }, category: "csaf_security_advisory", csaf_version: "2.0", distribution: { text: "Copyright 2024 SUSE LLC. All rights reserved.", tlp: { label: "WHITE", url: "https://www.first.org/tlp/", }, }, lang: "en", notes: [ { category: "summary", text: "Security update for haproxy", title: "Title of the patch", }, { category: "description", text: "\n \nThis update for haproxy to version 2.0.5+git0.d905f49a fixes the following issues:\n\nSecurity issue fixed:\n\n- CVE-2019-14241: Fixed a cookie memory corruption problem. (bsc#1142529)\n\nThe update to 2.0.5 brings lots of features and bugfixes:\n\n- new internal native HTTP representation called HTX, was already in 1.9 and is now enabled by default in 2.0\n- end-to-end HTTP/2 support including trailers and continuation frames, as needed for gRPC ; HTTP/2 may also be upgraded from HTTP/1.1 using the H2 preface;\n- server connection pooling and more advanced reuse, with ALPN protocol negotiation (already in 1.9)\n- layer 7 retries, allowing to use 0-RTT and TCP Fast Open to the servers as well as on the frontend\n- much more scalable multi-threading, which is even enabled by default on platforms where it was successfully tested ; by default, as many threads are started as the number of CPUs haproxy is allowed to run on. This removes a lot of configuration burden in VMs and containers\n- automatic maxconn setting for the process and the frontends, directly based on the number of available FDs (easier configuration in containers and with systemd)\n- logging to stdout for use in containers and systemd (already in 1.9). Logs can now provide micro-second resolution for some events\n- peers now support SSL, declaration of multiple stick-tables directly in the peers section, and synchronization of server names, not just IDs\n- In master-worker mode, the master process now exposes its own CLI and can communicate with all other processes (including the stopping ones), even allowing to connect to their CLI and check their state. It is also possible to start some sidecar programs and monitor them from the master, and the master can automatically kill old processes that survived too many reloads\n- the incoming connections are load-balanced between all threads depending on their load to minimize the processing time and maximize the capacity (already in 1.9)\n- the SPOE connection load-balancing was significantly improved in order to reduce high percentiles of SPOA response time (already in 1.9)\n- the 'random' load balancing algorithm and a power-of-two-choices variant were introduced\n- statistics improvements with per-thread counters for certain things, and a prometheus exporter for all our statistics;\n- lots of debugging help, it's easier to produce a core dump, there are new commands on the CLI to control various things, there is a watchdog to fail cleanly when a thread deadlock or a spinning task are detected, so overall it should provide a better experience in field and less round trips between users and developers (hence less stress during an incident).\n- all 3 device detection engines are now compatible with multi-threading and can be build-tested without any external dependencies\n- 'do-resolve' http-request action to perform a DNS resolution on any, sample, and resolvers now support relying on /etc/resolv.conf to match the local resolver\n- log sampling and balancing : it's now possible to send 1 log every 10 to a server, or to spread the logging load over multiple log servers;\n- a new SPOA agent (spoa_server) allows to interface haproxy with Python and Lua programs\n- support for Solaris' event ports (equivalent of kqueue or epoll) which will significantly improve the performance there when dealing with numerous connections\n- some warnings are now reported for some deprecated options that will be removed in 2.1. Since 2.0 is long term supported, there's no emergency to convert them, however if you see these warnings, you need to understand that you're among their extremely rare users and just because of this you may be taking risks by keeping them\n- A new SOCKS4 server-side layer was provided ; it allows outgoing connections to be forwarded through a SOCKS4 proxy (such as ssh -D).\n- priority- and latency- aware server queues : it is possible now to assign priorities to certain requests and/or to give them a time bonus or penalty to refine control of the traffic and be able to engage on SLAs.\n- internally the architecture was significantly redesigned to allow to further improve performance and make it easier to implement protocols that span over multiple layers (such as QUIC). This work started in 1.9 and will continue with 2.1.\n- the I/O, applets and tasks now share the same multi-threaded scheduler, giving a much better responsiveness and fairness between all tasks as is visible with the CLI which always responds instantly even under extreme loads (started in 1.9)\n- the internal buffers were redesigned to ease zero-copy operations, so that it is possible to sustain a high bandwidth even when forwarding HTTP/1 to/from HTTP/2 (already in 1.9)\n\n", title: "Description of the patch", }, { category: "details", text: "SUSE-2019-3002,SUSE-SLE-Product-HA-15-2019-3002", title: "Patchnames", }, { category: "legal_disclaimer", text: "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).", title: "Terms of use", }, ], publisher: { category: "vendor", contact_details: "https://www.suse.com/support/security/contact/", name: "SUSE Product Security Team", namespace: "https://www.suse.com/", }, references: [ { category: "external", summary: "SUSE ratings", url: "https://www.suse.com/support/security/rating/", }, { category: "self", summary: "URL of this CSAF notice", url: "https://ftp.suse.com/pub/projects/security/csaf/suse-su-2019_3002-1.json", }, { category: "self", summary: "URL for SUSE-SU-2019:3002-1", url: "https://www.suse.com/support/update/announcement/2019/suse-su-20193002-1/", }, { category: "self", summary: "E-Mail link for SUSE-SU-2019:3002-1", url: "https://lists.suse.com/pipermail/sle-security-updates/2019-November/006154.html", }, { category: "self", summary: "SUSE Bug 1142529", url: "https://bugzilla.suse.com/1142529", }, { category: "self", summary: "SUSE CVE CVE-2019-14241 page", url: "https://www.suse.com/security/cve/CVE-2019-14241/", }, { category: "self", summary: "SUSE Bug ECO-546", url: "https://bugzilla.suse.com/ECO-546", }, ], title: "Security update for haproxy", tracking: { current_release_date: "2019-11-18T16:10:45Z", generator: { date: "2019-11-18T16:10:45Z", engine: { name: "cve-database.git:bin/generate-csaf.pl", version: "1", }, }, id: "SUSE-SU-2019:3002-1", initial_release_date: "2019-11-18T16:10:45Z", revision_history: [ { date: "2019-11-18T16:10:45Z", number: "1", summary: "Current version", }, ], status: "final", version: "1", }, }, product_tree: { branches: [ { branches: [ { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64", product: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64", product_id: "haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64", }, }, ], category: "architecture", name: "aarch64", }, { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-3.12.6.i586", product: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.i586", product_id: "haproxy-2.0.5+git0.d905f49a-3.12.6.i586", }, }, ], category: "architecture", name: "i586", }, { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le", product: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le", product_id: "haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le", }, }, ], category: "architecture", name: "ppc64le", }, { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-3.12.6.s390x", product: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.s390x", product_id: "haproxy-2.0.5+git0.d905f49a-3.12.6.s390x", }, }, ], category: "architecture", name: "s390x", }, { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64", product: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64", product_id: "haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64", }, }, ], category: "architecture", name: "x86_64", }, { branches: [ { category: "product_name", name: "SUSE Linux Enterprise High Availability Extension 15", product: { name: "SUSE Linux Enterprise High Availability Extension 15", product_id: "SUSE Linux Enterprise High Availability Extension 15", product_identification_helper: { cpe: "cpe:/o:suse:sle-ha:15", }, }, }, ], category: "product_family", name: "SUSE Linux Enterprise", }, ], category: "vendor", name: "SUSE", }, ], relationships: [ { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64 as component of SUSE Linux Enterprise High Availability Extension 15", product_id: "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64", }, product_reference: "haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64", relates_to_product_reference: "SUSE Linux Enterprise High Availability Extension 15", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le as component of SUSE Linux Enterprise High Availability Extension 15", product_id: "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le", }, product_reference: "haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le", relates_to_product_reference: "SUSE Linux Enterprise High Availability Extension 15", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.s390x as component of SUSE Linux Enterprise High Availability Extension 15", product_id: "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.s390x", }, product_reference: "haproxy-2.0.5+git0.d905f49a-3.12.6.s390x", relates_to_product_reference: "SUSE Linux Enterprise High Availability Extension 15", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64 as component of SUSE Linux Enterprise High Availability Extension 15", product_id: "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64", }, product_reference: "haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64", relates_to_product_reference: "SUSE Linux Enterprise High Availability Extension 15", }, ], }, vulnerabilities: [ { cve: "CVE-2019-14241", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2019-14241", }, ], notes: [ { category: "general", text: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", title: "CVE description", }, ], product_status: { recommended: [ "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.s390x", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64", ], }, references: [ { category: "external", summary: "CVE-2019-14241", url: "https://www.suse.com/security/cve/CVE-2019-14241", }, { category: "external", summary: "SUSE Bug 1142529 for CVE-2019-14241", url: "https://bugzilla.suse.com/1142529", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.s390x", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, products: [ "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.aarch64", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.ppc64le", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.s390x", "SUSE Linux Enterprise High Availability Extension 15:haproxy-2.0.5+git0.d905f49a-3.12.6.x86_64", ], }, ], threats: [ { category: "impact", date: "2019-11-18T16:10:45Z", details: "important", }, ], title: "CVE-2019-14241", }, ], }
suse-su-2019:3001-1
Vulnerability from csaf_suse
Published
2019-11-18 16:10
Modified
2019-11-18 16:10
Summary
Security update for haproxy
Notes
Title of the patch
Security update for haproxy
Description of the patch
This update for haproxy to version 2.0.5+git0.d905f49a fixes the following issues:
Security issue fixed:
- CVE-2019-14241: Fixed a cookie memory corruption problem. (bsc#1142529)
The update to 2.0.5 brings lots of features and bugfixes:
- new internal native HTTP representation called HTX, was already in 1.9 and is now enabled by default in 2.0
- end-to-end HTTP/2 support including trailers and continuation frames, as needed for gRPC ; HTTP/2 may also be upgraded from HTTP/1.1 using the H2 preface;
- server connection pooling and more advanced reuse, with ALPN protocol negotiation (already in 1.9)
- layer 7 retries, allowing to use 0-RTT and TCP Fast Open to the servers as well as on the frontend
- much more scalable multi-threading, which is even enabled by default on platforms where it was successfully tested ; by default, as many threads are started as the number of CPUs haproxy is allowed to run on. This removes a lot of configuration burden in VMs and containers
- automatic maxconn setting for the process and the frontends, directly based on the number of available FDs (easier configuration in containers and with systemd)
- logging to stdout for use in containers and systemd (already in 1.9). Logs can now provide micro-second resolution for some events
- peers now support SSL, declaration of multiple stick-tables directly in the peers section, and synchronization of server names, not just IDs
- In master-worker mode, the master process now exposes its own CLI and can communicate with all other processes (including the stopping ones), even allowing to connect to their CLI and check their state. It is also possible to start some sidecar programs and monitor them from the master, and the master can automatically kill old processes that survived too many reloads
- the incoming connections are load-balanced between all threads depending on their load to minimize the processing time and maximize the capacity (already in 1.9)
- the SPOE connection load-balancing was significantly improved in order to reduce high percentiles of SPOA response time (already in 1.9)
- the 'random' load balancing algorithm and a power-of-two-choices variant were introduced
- statistics improvements with per-thread counters for certain things, and a prometheus exporter for all our statistics;
- lots of debugging help, it's easier to produce a core dump, there are new commands on the CLI to control various things, there is a watchdog to fail cleanly when a thread deadlock or a spinning task are detected, so overall it should provide a better experience in field and less round trips between users and developers (hence less stress during an incident).
- all 3 device detection engines are now compatible with multi-threading and can be build-tested without any external dependencies
- 'do-resolve' http-request action to perform a DNS resolution on any, sample, and resolvers now support relying on /etc/resolv.conf to match the local resolver
- log sampling and balancing : it's now possible to send 1 log every 10 to a server, or to spread the logging load over multiple log servers;
- a new SPOA agent (spoa_server) allows to interface haproxy with Python and Lua programs
- support for Solaris' event ports (equivalent of kqueue or epoll) which will significantly improve the performance there when dealing with numerous connections
- some warnings are now reported for some deprecated options that will be removed in 2.1. Since 2.0 is long term supported, there's no emergency to convert them, however if you see these warnings, you need to understand that you're among their extremely rare users and just because of this you may be taking risks by keeping them
- A new SOCKS4 server-side layer was provided ; it allows outgoing connections to be forwarded through a SOCKS4 proxy (such as ssh -D).
- priority- and latency- aware server queues : it is possible now to assign priorities to certain requests and/or to give them a time bonus or penalty to refine control of the traffic and be able to engage on SLAs.
- internally the architecture was significantly redesigned to allow to further improve performance and make it easier to implement protocols that span over multiple layers (such as QUIC). This work started in 1.9 and will continue with 2.1.
- the I/O, applets and tasks now share the same multi-threaded scheduler, giving a much better responsiveness and fairness between all tasks as is visible with the CLI which always responds instantly even under extreme loads (started in 1.9)
- the internal buffers were redesigned to ease zero-copy operations, so that it is possible to sustain a high bandwidth even when forwarding HTTP/1 to/from HTTP/2 (already in 1.9)
Patchnames
SUSE-2019-3001,SUSE-SLE-Product-HA-15-SP1-2019-3001
Terms of use
CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
{ document: { aggregate_severity: { namespace: "https://www.suse.com/support/security/rating/", text: "moderate", }, category: "csaf_security_advisory", csaf_version: "2.0", distribution: { text: "Copyright 2024 SUSE LLC. All rights reserved.", tlp: { label: "WHITE", url: "https://www.first.org/tlp/", }, }, lang: "en", notes: [ { category: "summary", text: "Security update for haproxy", title: "Title of the patch", }, { category: "description", text: "\n \nThis update for haproxy to version 2.0.5+git0.d905f49a fixes the following issues:\n\nSecurity issue fixed:\n\n- CVE-2019-14241: Fixed a cookie memory corruption problem. (bsc#1142529)\n\nThe update to 2.0.5 brings lots of features and bugfixes:\n\n- new internal native HTTP representation called HTX, was already in 1.9 and is now enabled by default in 2.0\n- end-to-end HTTP/2 support including trailers and continuation frames, as needed for gRPC ; HTTP/2 may also be upgraded from HTTP/1.1 using the H2 preface;\n- server connection pooling and more advanced reuse, with ALPN protocol negotiation (already in 1.9)\n- layer 7 retries, allowing to use 0-RTT and TCP Fast Open to the servers as well as on the frontend\n- much more scalable multi-threading, which is even enabled by default on platforms where it was successfully tested ; by default, as many threads are started as the number of CPUs haproxy is allowed to run on. This removes a lot of configuration burden in VMs and containers\n- automatic maxconn setting for the process and the frontends, directly based on the number of available FDs (easier configuration in containers and with systemd)\n- logging to stdout for use in containers and systemd (already in 1.9). Logs can now provide micro-second resolution for some events\n- peers now support SSL, declaration of multiple stick-tables directly in the peers section, and synchronization of server names, not just IDs\n- In master-worker mode, the master process now exposes its own CLI and can communicate with all other processes (including the stopping ones), even allowing to connect to their CLI and check their state. It is also possible to start some sidecar programs and monitor them from the master, and the master can automatically kill old processes that survived too many reloads\n- the incoming connections are load-balanced between all threads depending on their load to minimize the processing time and maximize the capacity (already in 1.9)\n- the SPOE connection load-balancing was significantly improved in order to reduce high percentiles of SPOA response time (already in 1.9)\n- the 'random' load balancing algorithm and a power-of-two-choices variant were introduced\n- statistics improvements with per-thread counters for certain things, and a prometheus exporter for all our statistics;\n- lots of debugging help, it's easier to produce a core dump, there are new commands on the CLI to control various things, there is a watchdog to fail cleanly when a thread deadlock or a spinning task are detected, so overall it should provide a better experience in field and less round trips between users and developers (hence less stress during an incident).\n- all 3 device detection engines are now compatible with multi-threading and can be build-tested without any external dependencies\n- 'do-resolve' http-request action to perform a DNS resolution on any, sample, and resolvers now support relying on /etc/resolv.conf to match the local resolver\n- log sampling and balancing : it's now possible to send 1 log every 10 to a server, or to spread the logging load over multiple log servers;\n- a new SPOA agent (spoa_server) allows to interface haproxy with Python and Lua programs\n- support for Solaris' event ports (equivalent of kqueue or epoll) which will significantly improve the performance there when dealing with numerous connections\n- some warnings are now reported for some deprecated options that will be removed in 2.1. Since 2.0 is long term supported, there's no emergency to convert them, however if you see these warnings, you need to understand that you're among their extremely rare users and just because of this you may be taking risks by keeping them\n- A new SOCKS4 server-side layer was provided ; it allows outgoing connections to be forwarded through a SOCKS4 proxy (such as ssh -D).\n- priority- and latency- aware server queues : it is possible now to assign priorities to certain requests and/or to give them a time bonus or penalty to refine control of the traffic and be able to engage on SLAs.\n- internally the architecture was significantly redesigned to allow to further improve performance and make it easier to implement protocols that span over multiple layers (such as QUIC). This work started in 1.9 and will continue with 2.1.\n- the I/O, applets and tasks now share the same multi-threaded scheduler, giving a much better responsiveness and fairness between all tasks as is visible with the CLI which always responds instantly even under extreme loads (started in 1.9)\n- the internal buffers were redesigned to ease zero-copy operations, so that it is possible to sustain a high bandwidth even when forwarding HTTP/1 to/from HTTP/2 (already in 1.9)\n\n", title: "Description of the patch", }, { category: "details", text: "SUSE-2019-3001,SUSE-SLE-Product-HA-15-SP1-2019-3001", title: "Patchnames", }, { category: "legal_disclaimer", text: "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).", title: "Terms of use", }, ], publisher: { category: "vendor", contact_details: "https://www.suse.com/support/security/contact/", name: "SUSE Product Security Team", namespace: "https://www.suse.com/", }, references: [ { category: "external", summary: "SUSE ratings", url: "https://www.suse.com/support/security/rating/", }, { category: "self", summary: "URL of this CSAF notice", url: "https://ftp.suse.com/pub/projects/security/csaf/suse-su-2019_3001-1.json", }, { category: "self", summary: "URL for SUSE-SU-2019:3001-1", url: "https://www.suse.com/support/update/announcement/2019/suse-su-20193001-1/", }, { category: "self", summary: "E-Mail link for SUSE-SU-2019:3001-1", url: "https://lists.suse.com/pipermail/sle-security-updates/2019-November/006153.html", }, { category: "self", summary: "SUSE Bug 1142529", url: "https://bugzilla.suse.com/1142529", }, { category: "self", summary: "SUSE CVE CVE-2019-14241 page", url: "https://www.suse.com/security/cve/CVE-2019-14241/", }, { category: "self", summary: "SUSE Bug ECO-546", url: "https://bugzilla.suse.com/ECO-546", }, ], title: "Security update for haproxy", tracking: { current_release_date: "2019-11-18T16:10:13Z", generator: { date: "2019-11-18T16:10:13Z", engine: { name: "cve-database.git:bin/generate-csaf.pl", version: "1", }, }, id: "SUSE-SU-2019:3001-1", initial_release_date: "2019-11-18T16:10:13Z", revision_history: [ { date: "2019-11-18T16:10:13Z", number: "1", summary: "Current version", }, ], status: "final", version: "1", }, }, product_tree: { branches: [ { branches: [ { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64", product: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64", product_id: "haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64", }, }, ], category: "architecture", name: "aarch64", }, { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-8.3.5.i586", product: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.i586", product_id: "haproxy-2.0.5+git0.d905f49a-8.3.5.i586", }, }, ], category: "architecture", name: "i586", }, { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le", product: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le", product_id: "haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le", }, }, ], category: "architecture", name: "ppc64le", }, { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-8.3.5.s390x", product: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.s390x", product_id: "haproxy-2.0.5+git0.d905f49a-8.3.5.s390x", }, }, ], category: "architecture", name: "s390x", }, { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64", product: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64", product_id: "haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64", }, }, ], category: "architecture", name: "x86_64", }, { branches: [ { category: "product_name", name: "SUSE Linux Enterprise High Availability Extension 15 SP1", product: { name: "SUSE Linux Enterprise High Availability Extension 15 SP1", product_id: "SUSE Linux Enterprise High Availability Extension 15 SP1", product_identification_helper: { cpe: "cpe:/o:suse:sle-ha:15:sp1", }, }, }, ], category: "product_family", name: "SUSE Linux Enterprise", }, ], category: "vendor", name: "SUSE", }, ], relationships: [ { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64 as component of SUSE Linux Enterprise High Availability Extension 15 SP1", product_id: "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64", }, product_reference: "haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64", relates_to_product_reference: "SUSE Linux Enterprise High Availability Extension 15 SP1", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le as component of SUSE Linux Enterprise High Availability Extension 15 SP1", product_id: "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le", }, product_reference: "haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le", relates_to_product_reference: "SUSE Linux Enterprise High Availability Extension 15 SP1", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.s390x as component of SUSE Linux Enterprise High Availability Extension 15 SP1", product_id: "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.s390x", }, product_reference: "haproxy-2.0.5+git0.d905f49a-8.3.5.s390x", relates_to_product_reference: "SUSE Linux Enterprise High Availability Extension 15 SP1", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64 as component of SUSE Linux Enterprise High Availability Extension 15 SP1", product_id: "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64", }, product_reference: "haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64", relates_to_product_reference: "SUSE Linux Enterprise High Availability Extension 15 SP1", }, ], }, vulnerabilities: [ { cve: "CVE-2019-14241", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2019-14241", }, ], notes: [ { category: "general", text: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", title: "CVE description", }, ], product_status: { recommended: [ "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.s390x", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64", ], }, references: [ { category: "external", summary: "CVE-2019-14241", url: "https://www.suse.com/security/cve/CVE-2019-14241", }, { category: "external", summary: "SUSE Bug 1142529 for CVE-2019-14241", url: "https://bugzilla.suse.com/1142529", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.s390x", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, products: [ "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.aarch64", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.ppc64le", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.s390x", "SUSE Linux Enterprise High Availability Extension 15 SP1:haproxy-2.0.5+git0.d905f49a-8.3.5.x86_64", ], }, ], threats: [ { category: "impact", date: "2019-11-18T16:10:13Z", details: "important", }, ], title: "CVE-2019-14241", }, ], }
wid-sec-w-2024-0054
Vulnerability from csaf_certbund
Published
2024-01-09 23:00
Modified
2024-01-09 23:00
Summary
IBM Security Verify Access: Mehrere Schwachstellen
Notes
Das BSI ist als Anbieter für die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch dafür verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgfältig im Einzelfall zu prüfen.
Produktbeschreibung
IBM Security Verify Access, ehemals IBM Security Access Manager (ISAM), ist eine Zugriffsverwaltungslösung.
Angriff
Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen.
Betroffene Betriebssysteme
- Sonstiges
{ document: { aggregate_severity: { text: "hoch", }, category: "csaf_base", csaf_version: "2.0", distribution: { tlp: { label: "WHITE", url: "https://www.first.org/tlp/", }, }, lang: "de-DE", notes: [ { category: "legal_disclaimer", text: "Das BSI ist als Anbieter für die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch dafür verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgfältig im Einzelfall zu prüfen.", }, { category: "description", text: "IBM Security Verify Access, ehemals IBM Security Access Manager (ISAM), ist eine Zugriffsverwaltungslösung.", title: "Produktbeschreibung", }, { category: "summary", text: "Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen.", title: "Angriff", }, { category: "general", text: "- Sonstiges", title: "Betroffene Betriebssysteme", }, ], publisher: { category: "other", contact_details: "csaf-provider@cert-bund.de", name: "Bundesamt für Sicherheit in der Informationstechnik", namespace: "https://www.bsi.bund.de", }, references: [ { category: "self", summary: "WID-SEC-W-2024-0054 - CSAF Version", url: "https://wid.cert-bund.de/.well-known/csaf/white/2024/wid-sec-w-2024-0054.json", }, { category: "self", summary: "WID-SEC-2024-0054 - Portal Version", url: "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-0054", }, { category: "external", summary: "IBM Security Bulletin 7106586 vom 2024-01-09", url: "https://www.ibm.com/support/pages/node/7106586", }, { category: "external", summary: "IBM Security Bulletin 7106583 vom 2024-01-09", url: "https://www.ibm.com/support/pages/node/7106583", }, ], source_lang: "en-US", title: "IBM Security Verify Access: Mehrere Schwachstellen", tracking: { current_release_date: "2024-01-09T23:00:00.000+00:00", generator: { date: "2024-08-15T18:03:29.433+00:00", engine: { name: "BSI-WID", version: "1.3.5", }, }, id: "WID-SEC-W-2024-0054", initial_release_date: "2024-01-09T23:00:00.000+00:00", revision_history: [ { date: "2024-01-09T23:00:00.000+00:00", number: "1", summary: "Initiale Fassung", }, ], status: "final", version: "1", }, }, product_tree: { branches: [ { branches: [ { category: "product_name", name: "IBM Security Verify Access < 10.0.7-ISS-ISVA-FP0000", product: { name: "IBM Security Verify Access < 10.0.7-ISS-ISVA-FP0000", product_id: "T031968", product_identification_helper: { cpe: "cpe:/a:ibm:security_verify_access:10.0.7-iss-isva-fp0000", }, }, }, ], category: "vendor", name: "IBM", }, ], }, vulnerabilities: [ { cve: "CVE-2032-43016", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2032-43016", }, { cve: "CVE-2023-43017", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-43017", }, { cve: "CVE-2023-40225", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-40225", }, { cve: "CVE-2023-39417", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-39417", }, { cve: "CVE-2023-38369", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-38369", }, { cve: "CVE-2023-38267", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-38267", }, { cve: "CVE-2023-32697", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32697", }, { cve: "CVE-2023-32330", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32330", }, { cve: "CVE-2023-32329", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32329", }, { cve: "CVE-2023-32328", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32328", }, { cve: "CVE-2023-32327", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32327", }, { cve: "CVE-2023-31006", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31006", }, { cve: "CVE-2023-31005", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31005", }, { cve: "CVE-2023-31004", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31004", }, { cve: "CVE-2023-31003", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31003", }, { cve: "CVE-2023-31002", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31002", }, { cve: "CVE-2023-31001", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31001", }, { cve: "CVE-2023-30999", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-30999", }, { cve: "CVE-2023-25725", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-25725", }, { cve: "CVE-2023-24998", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-24998", }, { cve: "CVE-2023-2455", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-2455", }, { cve: "CVE-2023-2454", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-2454", }, { cve: "CVE-2023-1370", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-1370", }, { cve: "CVE-2022-45688", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-45688", }, { cve: "CVE-2022-41862", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-41862", }, { cve: "CVE-2022-2625", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-2625", }, { cve: "CVE-2022-2068", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-2068", }, { cve: "CVE-2022-1471", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-1471", }, { cve: "CVE-2020-11100", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2020-11100", }, { cve: "CVE-2019-19330", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2019-19330", }, { cve: "CVE-2019-18277", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2019-18277", }, { cve: "CVE-2019-18276", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2019-18276", }, { cve: "CVE-2019-14241", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2019-14241", }, { cve: "CVE-2017-18342", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2017-18342", }, { cve: "CVE-2015-5237", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2015-5237", }, ], }
WID-SEC-W-2024-0054
Vulnerability from csaf_certbund
Published
2024-01-09 23:00
Modified
2024-01-09 23:00
Summary
IBM Security Verify Access: Mehrere Schwachstellen
Notes
Das BSI ist als Anbieter für die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch dafür verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgfältig im Einzelfall zu prüfen.
Produktbeschreibung
IBM Security Verify Access, ehemals IBM Security Access Manager (ISAM), ist eine Zugriffsverwaltungslösung.
Angriff
Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen.
Betroffene Betriebssysteme
- Sonstiges
{ document: { aggregate_severity: { text: "hoch", }, category: "csaf_base", csaf_version: "2.0", distribution: { tlp: { label: "WHITE", url: "https://www.first.org/tlp/", }, }, lang: "de-DE", notes: [ { category: "legal_disclaimer", text: "Das BSI ist als Anbieter für die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch dafür verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgfältig im Einzelfall zu prüfen.", }, { category: "description", text: "IBM Security Verify Access, ehemals IBM Security Access Manager (ISAM), ist eine Zugriffsverwaltungslösung.", title: "Produktbeschreibung", }, { category: "summary", text: "Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen.", title: "Angriff", }, { category: "general", text: "- Sonstiges", title: "Betroffene Betriebssysteme", }, ], publisher: { category: "other", contact_details: "csaf-provider@cert-bund.de", name: "Bundesamt für Sicherheit in der Informationstechnik", namespace: "https://www.bsi.bund.de", }, references: [ { category: "self", summary: "WID-SEC-W-2024-0054 - CSAF Version", url: "https://wid.cert-bund.de/.well-known/csaf/white/2024/wid-sec-w-2024-0054.json", }, { category: "self", summary: "WID-SEC-2024-0054 - Portal Version", url: "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-0054", }, { category: "external", summary: "IBM Security Bulletin 7106586 vom 2024-01-09", url: "https://www.ibm.com/support/pages/node/7106586", }, { category: "external", summary: "IBM Security Bulletin 7106583 vom 2024-01-09", url: "https://www.ibm.com/support/pages/node/7106583", }, ], source_lang: "en-US", title: "IBM Security Verify Access: Mehrere Schwachstellen", tracking: { current_release_date: "2024-01-09T23:00:00.000+00:00", generator: { date: "2024-08-15T18:03:29.433+00:00", engine: { name: "BSI-WID", version: "1.3.5", }, }, id: "WID-SEC-W-2024-0054", initial_release_date: "2024-01-09T23:00:00.000+00:00", revision_history: [ { date: "2024-01-09T23:00:00.000+00:00", number: "1", summary: "Initiale Fassung", }, ], status: "final", version: "1", }, }, product_tree: { branches: [ { branches: [ { category: "product_name", name: "IBM Security Verify Access < 10.0.7-ISS-ISVA-FP0000", product: { name: "IBM Security Verify Access < 10.0.7-ISS-ISVA-FP0000", product_id: "T031968", product_identification_helper: { cpe: "cpe:/a:ibm:security_verify_access:10.0.7-iss-isva-fp0000", }, }, }, ], category: "vendor", name: "IBM", }, ], }, vulnerabilities: [ { cve: "CVE-2032-43016", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2032-43016", }, { cve: "CVE-2023-43017", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-43017", }, { cve: "CVE-2023-40225", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-40225", }, { cve: "CVE-2023-39417", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-39417", }, { cve: "CVE-2023-38369", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-38369", }, { cve: "CVE-2023-38267", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-38267", }, { cve: "CVE-2023-32697", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32697", }, { cve: "CVE-2023-32330", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32330", }, { cve: "CVE-2023-32329", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32329", }, { cve: "CVE-2023-32328", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32328", }, { cve: "CVE-2023-32327", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-32327", }, { cve: "CVE-2023-31006", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31006", }, { cve: "CVE-2023-31005", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31005", }, { cve: "CVE-2023-31004", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31004", }, { cve: "CVE-2023-31003", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31003", }, { cve: "CVE-2023-31002", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31002", }, { cve: "CVE-2023-31001", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-31001", }, { cve: "CVE-2023-30999", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-30999", }, { cve: "CVE-2023-25725", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-25725", }, { cve: "CVE-2023-24998", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-24998", }, { cve: "CVE-2023-2455", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-2455", }, { cve: "CVE-2023-2454", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-2454", }, { cve: "CVE-2023-1370", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2023-1370", }, { cve: "CVE-2022-45688", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-45688", }, { cve: "CVE-2022-41862", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-41862", }, { cve: "CVE-2022-2625", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-2625", }, { cve: "CVE-2022-2068", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-2068", }, { cve: "CVE-2022-1471", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2022-1471", }, { cve: "CVE-2020-11100", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2020-11100", }, { cve: "CVE-2019-19330", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2019-19330", }, { cve: "CVE-2019-18277", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2019-18277", }, { cve: "CVE-2019-18276", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2019-18276", }, { cve: "CVE-2019-14241", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2019-14241", }, { cve: "CVE-2017-18342", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2017-18342", }, { cve: "CVE-2015-5237", notes: [ { category: "description", text: "Es bestehen mehrere Schwachstellen in IBM Security Verify Access. Diese Fehler bestehen in mehreren Komponenten wie Access Manager Container und Drittanbieter-Modulen wie PostgreSQL oder HAProxy. Ein Angreifer kann diese Schwachstellen ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder komplexe Angriffe wie Cache-Poisoning, Cross-Site-Scripting oder Session-Hijacking durchzuführen. Einige der Schwachstellen erfordern eine Interaktion des Benutzers, um sie erfolgreich auszunutzen.", }, ], release_date: "2024-01-09T23:00:00.000+00:00", title: "CVE-2015-5237", }, ], }
opensuse-su-2019:2556-1
Vulnerability from csaf_opensuse
Published
2019-11-23 19:23
Modified
2019-11-23 19:23
Summary
Security update for haproxy
Notes
Title of the patch
Security update for haproxy
Description of the patch
This update for haproxy to version 2.0.5+git0.d905f49a fixes the following issues:
Security issue fixed:
- CVE-2019-14241: Fixed a cookie memory corruption problem. (bsc#1142529)
The update to 2.0.5 brings lots of features and bugfixes:
- new internal native HTTP representation called HTX, was already in 1.9 and is now enabled by default in 2.0
- end-to-end HTTP/2 support including trailers and continuation frames, as needed for gRPC ; HTTP/2 may also be upgraded from HTTP/1.1 using the H2 preface;
- server connection pooling and more advanced reuse, with ALPN protocol negotiation (already in 1.9)
- layer 7 retries, allowing to use 0-RTT and TCP Fast Open to the servers as well as on the frontend
- much more scalable multi-threading, which is even enabled by default on platforms where it was successfully tested ; by default, as many threads are started as the number of CPUs haproxy is allowed to run on. This removes a lot of configuration burden in VMs and containers
- automatic maxconn setting for the process and the frontends, directly based on the number of available FDs (easier configuration in containers and with systemd)
- logging to stdout for use in containers and systemd (already in 1.9). Logs can now provide micro-second resolution for some events
- peers now support SSL, declaration of multiple stick-tables directly in the peers section, and synchronization of server names, not just IDs
- In master-worker mode, the master process now exposes its own CLI and can communicate with all other processes (including the stopping ones), even allowing to connect to their CLI and check their state. It is also possible to start some sidecar programs and monitor them from the master, and the master can automatically kill old processes that survived too many reloads
- the incoming connections are load-balanced between all threads depending on their load to minimize the processing time and maximize the capacity (already in 1.9)
- the SPOE connection load-balancing was significantly improved in order to reduce high percentiles of SPOA response time (already in 1.9)
- the 'random' load balancing algorithm and a power-of-two-choices variant were introduced
- statistics improvements with per-thread counters for certain things, and a prometheus exporter for all our statistics;
- lots of debugging help, it's easier to produce a core dump, there are new commands on the CLI to control various things, there is a watchdog to fail cleanly when a thread deadlock or a spinning task are detected, so overall it should provide a better experience in field and less round trips between users and developers (hence less stress during an incident).
- all 3 device detection engines are now compatible with multi-threading and can be build-tested without any external dependencies
- 'do-resolve' http-request action to perform a DNS resolution on any, sample, and resolvers now support relying on /etc/resolv.conf to match the local resolver
- log sampling and balancing : it's now possible to send 1 log every 10 to a server, or to spread the logging load over multiple log servers;
- a new SPOA agent (spoa_server) allows to interface haproxy with Python and Lua programs
- support for Solaris' event ports (equivalent of kqueue or epoll) which will significantly improve the performance there when dealing with numerous connections
- some warnings are now reported for some deprecated options that will be removed in 2.1. Since 2.0 is long term supported, there's no emergency to convert them, however if you see these warnings, you need to understand that you're among their extremely rare users and just because of this you may be taking risks by keeping them
- A new SOCKS4 server-side layer was provided ; it allows outgoing connections to be forwarded through a SOCKS4 proxy (such as ssh -D).
- priority- and latency- aware server queues : it is possible now to assign priorities to certain requests and/or to give them a time bonus or penalty to refine control of the traffic and be able to engage on SLAs.
- internally the architecture was significantly redesigned to allow to further improve performance and make it easier to implement protocols that span over multiple layers (such as QUIC). This work started in 1.9 and will continue with 2.1.
- the I/O, applets and tasks now share the same multi-threaded scheduler, giving a much better responsiveness and fairness between all tasks as is visible with the CLI which always responds instantly even under extreme loads (started in 1.9)
- the internal buffers were redesigned to ease zero-copy operations, so that it is possible to sustain a high bandwidth even when forwarding HTTP/1 to/from HTTP/2 (already in 1.9)
This update was imported from the SUSE:SLE-15-SP1:Update update project.
Patchnames
openSUSE-2019-2556
Terms of use
CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
{ document: { aggregate_severity: { namespace: "https://www.suse.com/support/security/rating/", text: "moderate", }, category: "csaf_security_advisory", csaf_version: "2.0", distribution: { text: "Copyright 2024 SUSE LLC. All rights reserved.", tlp: { label: "WHITE", url: "https://www.first.org/tlp/", }, }, lang: "en", notes: [ { category: "summary", text: "Security update for haproxy", title: "Title of the patch", }, { category: "description", text: "\n \nThis update for haproxy to version 2.0.5+git0.d905f49a fixes the following issues:\n\nSecurity issue fixed:\n\n- CVE-2019-14241: Fixed a cookie memory corruption problem. (bsc#1142529)\n\nThe update to 2.0.5 brings lots of features and bugfixes:\n\n- new internal native HTTP representation called HTX, was already in 1.9 and is now enabled by default in 2.0\n- end-to-end HTTP/2 support including trailers and continuation frames, as needed for gRPC ; HTTP/2 may also be upgraded from HTTP/1.1 using the H2 preface;\n- server connection pooling and more advanced reuse, with ALPN protocol negotiation (already in 1.9)\n- layer 7 retries, allowing to use 0-RTT and TCP Fast Open to the servers as well as on the frontend\n- much more scalable multi-threading, which is even enabled by default on platforms where it was successfully tested ; by default, as many threads are started as the number of CPUs haproxy is allowed to run on. This removes a lot of configuration burden in VMs and containers\n- automatic maxconn setting for the process and the frontends, directly based on the number of available FDs (easier configuration in containers and with systemd)\n- logging to stdout for use in containers and systemd (already in 1.9). Logs can now provide micro-second resolution for some events\n- peers now support SSL, declaration of multiple stick-tables directly in the peers section, and synchronization of server names, not just IDs\n- In master-worker mode, the master process now exposes its own CLI and can communicate with all other processes (including the stopping ones), even allowing to connect to their CLI and check their state. It is also possible to start some sidecar programs and monitor them from the master, and the master can automatically kill old processes that survived too many reloads\n- the incoming connections are load-balanced between all threads depending on their load to minimize the processing time and maximize the capacity (already in 1.9)\n- the SPOE connection load-balancing was significantly improved in order to reduce high percentiles of SPOA response time (already in 1.9)\n- the 'random' load balancing algorithm and a power-of-two-choices variant were introduced\n- statistics improvements with per-thread counters for certain things, and a prometheus exporter for all our statistics;\n- lots of debugging help, it's easier to produce a core dump, there are new commands on the CLI to control various things, there is a watchdog to fail cleanly when a thread deadlock or a spinning task are detected, so overall it should provide a better experience in field and less round trips between users and developers (hence less stress during an incident).\n- all 3 device detection engines are now compatible with multi-threading and can be build-tested without any external dependencies\n- 'do-resolve' http-request action to perform a DNS resolution on any, sample, and resolvers now support relying on /etc/resolv.conf to match the local resolver\n- log sampling and balancing : it's now possible to send 1 log every 10 to a server, or to spread the logging load over multiple log servers;\n- a new SPOA agent (spoa_server) allows to interface haproxy with Python and Lua programs\n- support for Solaris' event ports (equivalent of kqueue or epoll) which will significantly improve the performance there when dealing with numerous connections\n- some warnings are now reported for some deprecated options that will be removed in 2.1. Since 2.0 is long term supported, there's no emergency to convert them, however if you see these warnings, you need to understand that you're among their extremely rare users and just because of this you may be taking risks by keeping them\n- A new SOCKS4 server-side layer was provided ; it allows outgoing connections to be forwarded through a SOCKS4 proxy (such as ssh -D).\n- priority- and latency- aware server queues : it is possible now to assign priorities to certain requests and/or to give them a time bonus or penalty to refine control of the traffic and be able to engage on SLAs.\n- internally the architecture was significantly redesigned to allow to further improve performance and make it easier to implement protocols that span over multiple layers (such as QUIC). This work started in 1.9 and will continue with 2.1.\n- the I/O, applets and tasks now share the same multi-threaded scheduler, giving a much better responsiveness and fairness between all tasks as is visible with the CLI which always responds instantly even under extreme loads (started in 1.9)\n- the internal buffers were redesigned to ease zero-copy operations, so that it is possible to sustain a high bandwidth even when forwarding HTTP/1 to/from HTTP/2 (already in 1.9)\n\n\nThis update was imported from the SUSE:SLE-15-SP1:Update update project.", title: "Description of the patch", }, { category: "details", text: "openSUSE-2019-2556", title: "Patchnames", }, { category: "legal_disclaimer", text: "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).", title: "Terms of use", }, ], publisher: { category: "vendor", contact_details: "https://www.suse.com/support/security/contact/", name: "SUSE Product Security Team", namespace: "https://www.suse.com/", }, references: [ { category: "external", summary: "SUSE ratings", url: "https://www.suse.com/support/security/rating/", }, { category: "self", summary: "URL of this CSAF notice", url: "https://ftp.suse.com/pub/projects/security/csaf/opensuse-su-2019_2556-1.json", }, { category: "self", summary: "URL for openSUSE-SU-2019:2556-1", url: "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/FUKOGLVYHSIG27DU7HAIRPPNF5XBHVDD/#FUKOGLVYHSIG27DU7HAIRPPNF5XBHVDD", }, { category: "self", summary: "E-Mail link for openSUSE-SU-2019:2556-1", url: "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/FUKOGLVYHSIG27DU7HAIRPPNF5XBHVDD/#FUKOGLVYHSIG27DU7HAIRPPNF5XBHVDD", }, { category: "self", summary: "SUSE Bug 1142529", url: "https://bugzilla.suse.com/1142529", }, { category: "self", summary: "SUSE CVE CVE-2019-14241 page", url: "https://www.suse.com/security/cve/CVE-2019-14241/", }, ], title: "Security update for haproxy", tracking: { current_release_date: "2019-11-23T19:23:07Z", generator: { date: "2019-11-23T19:23:07Z", engine: { name: "cve-database.git:bin/generate-csaf.pl", version: "1", }, }, id: "openSUSE-SU-2019:2556-1", initial_release_date: "2019-11-23T19:23:07Z", revision_history: [ { date: "2019-11-23T19:23:07Z", number: "1", summary: "Current version", }, ], status: "final", version: "1", }, }, product_tree: { branches: [ { branches: [ { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64", product: { name: "haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64", product_id: "haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64", }, }, ], category: "architecture", name: "x86_64", }, { branches: [ { category: "product_name", name: "openSUSE Leap 15.1", product: { name: "openSUSE Leap 15.1", product_id: "openSUSE Leap 15.1", product_identification_helper: { cpe: "cpe:/o:opensuse:leap:15.1", }, }, }, ], category: "product_family", name: "SUSE Linux Enterprise", }, ], category: "vendor", name: "SUSE", }, ], relationships: [ { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64 as component of openSUSE Leap 15.1", product_id: "openSUSE Leap 15.1:haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64", }, product_reference: "haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64", relates_to_product_reference: "openSUSE Leap 15.1", }, ], }, vulnerabilities: [ { cve: "CVE-2019-14241", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2019-14241", }, ], notes: [ { category: "general", text: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Leap 15.1:haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64", ], }, references: [ { category: "external", summary: "CVE-2019-14241", url: "https://www.suse.com/security/cve/CVE-2019-14241", }, { category: "external", summary: "SUSE Bug 1142529 for CVE-2019-14241", url: "https://bugzilla.suse.com/1142529", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Leap 15.1:haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, products: [ "openSUSE Leap 15.1:haproxy-2.0.5+git0.d905f49a-lp151.2.3.1.x86_64", ], }, ], threats: [ { category: "impact", date: "2019-11-23T19:23:07Z", details: "important", }, ], title: "CVE-2019-14241", }, ], }
opensuse-su-2024:10839-1
Vulnerability from csaf_opensuse
Published
2024-06-15 00:00
Modified
2024-06-15 00:00
Summary
haproxy-2.4.4+git0.acb1d0bea-1.2 on GA media
Notes
Title of the patch
haproxy-2.4.4+git0.acb1d0bea-1.2 on GA media
Description of the patch
These are all security issues fixed in the haproxy-2.4.4+git0.acb1d0bea-1.2 package on the GA media of openSUSE Tumbleweed.
Patchnames
openSUSE-Tumbleweed-2024-10839
Terms of use
CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
{ document: { aggregate_severity: { namespace: "https://www.suse.com/support/security/rating/", text: "moderate", }, category: "csaf_security_advisory", csaf_version: "2.0", distribution: { text: "Copyright 2024 SUSE LLC. All rights reserved.", tlp: { label: "WHITE", url: "https://www.first.org/tlp/", }, }, lang: "en", notes: [ { category: "summary", text: "haproxy-2.4.4+git0.acb1d0bea-1.2 on GA media", title: "Title of the patch", }, { category: "description", text: "These are all security issues fixed in the haproxy-2.4.4+git0.acb1d0bea-1.2 package on the GA media of openSUSE Tumbleweed.", title: "Description of the patch", }, { category: "details", text: "openSUSE-Tumbleweed-2024-10839", title: "Patchnames", }, { category: "legal_disclaimer", text: "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).", title: "Terms of use", }, ], publisher: { category: "vendor", contact_details: "https://www.suse.com/support/security/contact/", name: "SUSE Product Security Team", namespace: "https://www.suse.com/", }, references: [ { category: "external", summary: "SUSE ratings", url: "https://www.suse.com/support/security/rating/", }, { category: "self", summary: "URL of this CSAF notice", url: "https://ftp.suse.com/pub/projects/security/csaf/opensuse-su-2024_10839-1.json", }, { category: "self", summary: "SUSE CVE CVE-2018-11469 page", url: "https://www.suse.com/security/cve/CVE-2018-11469/", }, { category: "self", summary: "SUSE CVE CVE-2018-14645 page", url: "https://www.suse.com/security/cve/CVE-2018-14645/", }, { category: "self", summary: "SUSE CVE CVE-2018-20103 page", url: "https://www.suse.com/security/cve/CVE-2018-20103/", }, { category: "self", summary: "SUSE CVE CVE-2018-20615 page", url: "https://www.suse.com/security/cve/CVE-2018-20615/", }, { category: "self", summary: "SUSE CVE CVE-2019-14241 page", url: "https://www.suse.com/security/cve/CVE-2019-14241/", }, { category: "self", summary: "SUSE CVE CVE-2019-18277 page", url: "https://www.suse.com/security/cve/CVE-2019-18277/", }, { category: "self", summary: "SUSE CVE CVE-2020-11100 page", url: "https://www.suse.com/security/cve/CVE-2020-11100/", }, { category: "self", summary: "SUSE CVE CVE-2021-39240 page", url: "https://www.suse.com/security/cve/CVE-2021-39240/", }, { category: "self", summary: "SUSE CVE CVE-2021-40346 page", url: "https://www.suse.com/security/cve/CVE-2021-40346/", }, ], title: "haproxy-2.4.4+git0.acb1d0bea-1.2 on GA media", tracking: { current_release_date: "2024-06-15T00:00:00Z", generator: { date: "2024-06-15T00:00:00Z", engine: { name: "cve-database.git:bin/generate-csaf.pl", version: "1", }, }, id: "openSUSE-SU-2024:10839-1", initial_release_date: "2024-06-15T00:00:00Z", revision_history: [ { date: "2024-06-15T00:00:00Z", number: "1", summary: "Current version", }, ], status: "final", version: "1", }, }, product_tree: { branches: [ { branches: [ { branches: [ { category: "product_version", name: "haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", product: { name: "haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", product_id: "haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", }, }, ], category: "architecture", name: "aarch64", }, { branches: [ { category: "product_version", name: "haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", product: { name: "haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", product_id: "haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", }, }, ], category: "architecture", name: "ppc64le", }, { branches: [ { category: "product_version", name: "haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", product: { name: "haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", product_id: "haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", }, }, ], category: "architecture", name: "s390x", }, { branches: [ { category: "product_version", name: "haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", product: { name: "haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", product_id: "haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", }, }, ], category: "architecture", name: "x86_64", }, { branches: [ { category: "product_name", name: "openSUSE Tumbleweed", product: { name: "openSUSE Tumbleweed", product_id: "openSUSE Tumbleweed", product_identification_helper: { cpe: "cpe:/o:opensuse:tumbleweed", }, }, }, ], category: "product_family", name: "SUSE Linux Enterprise", }, ], category: "vendor", name: "SUSE", }, ], relationships: [ { category: "default_component_of", full_product_name: { name: "haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64 as component of openSUSE Tumbleweed", product_id: "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", }, product_reference: "haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", relates_to_product_reference: "openSUSE Tumbleweed", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le as component of openSUSE Tumbleweed", product_id: "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", }, product_reference: "haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", relates_to_product_reference: "openSUSE Tumbleweed", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.4.4+git0.acb1d0bea-1.2.s390x as component of openSUSE Tumbleweed", product_id: "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", }, product_reference: "haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", relates_to_product_reference: "openSUSE Tumbleweed", }, { category: "default_component_of", full_product_name: { name: "haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64 as component of openSUSE Tumbleweed", product_id: "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", }, product_reference: "haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", relates_to_product_reference: "openSUSE Tumbleweed", }, ], }, vulnerabilities: [ { cve: "CVE-2018-11469", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2018-11469", }, ], notes: [ { category: "general", text: "Incorrect caching of responses to requests including an Authorization header in HAProxy 1.8.0 through 1.8.9 (if cache enabled) allows attackers to achieve information disclosure via an unauthenticated remote request, related to the proto_http.c check_request_for_cacheability function.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2018-11469", url: "https://www.suse.com/security/cve/CVE-2018-11469", }, { category: "external", summary: "SUSE Bug 1094846 for CVE-2018-11469", url: "https://bugzilla.suse.com/1094846", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 5.3, baseSeverity: "MEDIUM", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", version: "3.0", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "moderate", }, ], title: "CVE-2018-11469", }, { cve: "CVE-2018-14645", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2018-14645", }, ], notes: [ { category: "general", text: "A flaw was discovered in the HPACK decoder of HAProxy, before 1.8.14, that is used for HTTP/2. An out-of-bounds read access in hpack_valid_idx() resulted in a remote crash and denial of service.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2018-14645", url: "https://www.suse.com/security/cve/CVE-2018-14645", }, { category: "external", summary: "SUSE Bug 1108683 for CVE-2018-14645", url: "https://bugzilla.suse.com/1108683", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "important", }, ], title: "CVE-2018-14645", }, { cve: "CVE-2018-20103", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2018-20103", }, ], notes: [ { category: "general", text: "An issue was discovered in dns.c in HAProxy through 1.8.14. In the case of a compressed pointer, a crafted packet can trigger infinite recursion by making the pointer point to itself, or create a long chain of valid pointers resulting in stack exhaustion.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2018-20103", url: "https://www.suse.com/security/cve/CVE-2018-20103", }, { category: "external", summary: "SUSE Bug 1119419 for CVE-2018-20103", url: "https://bugzilla.suse.com/1119419", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "important", }, ], title: "CVE-2018-20103", }, { cve: "CVE-2018-20615", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2018-20615", }, ], notes: [ { category: "general", text: "An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. The processing of the PRIORITY flag in a HEADERS frame requires 5 extra bytes, and while these bytes are skipped, the total frame length was not re-checked to make sure they were present in the frame.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2018-20615", url: "https://www.suse.com/security/cve/CVE-2018-20615", }, { category: "external", summary: "SUSE Bug 1121283 for CVE-2018-20615", url: "https://bugzilla.suse.com/1121283", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 8.2, baseSeverity: "HIGH", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H", version: "3.0", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "important", }, ], title: "CVE-2018-20615", }, { cve: "CVE-2019-14241", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2019-14241", }, ], notes: [ { category: "general", text: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2019-14241", url: "https://www.suse.com/security/cve/CVE-2019-14241", }, { category: "external", summary: "SUSE Bug 1142529 for CVE-2019-14241", url: "https://bugzilla.suse.com/1142529", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "important", }, ], title: "CVE-2019-14241", }, { cve: "CVE-2019-18277", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2019-18277", }, ], notes: [ { category: "general", text: "A flaw was found in HAProxy before 2.0.6. In legacy mode, messages featuring a transfer-encoding header missing the \"chunked\" value were not being correctly rejected. The impact was limited but if combined with the \"http-reuse always\" setting, it could be used to help construct an HTTP request smuggling attack against a vulnerable component employing a lenient parser that would ignore the content-length header as soon as it saw a transfer-encoding one (even if not entirely valid according to the specification).", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2019-18277", url: "https://www.suse.com/security/cve/CVE-2019-18277", }, { category: "external", summary: "SUSE Bug 1154980 for CVE-2019-18277", url: "https://bugzilla.suse.com/1154980", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 5.9, baseSeverity: "MEDIUM", vectorString: "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N", version: "3.0", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "moderate", }, ], title: "CVE-2019-18277", }, { cve: "CVE-2020-11100", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2020-11100", }, ], notes: [ { category: "general", text: "In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain location on the heap via a crafted HTTP/2 request, possibly causing remote code execution.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2020-11100", url: "https://www.suse.com/security/cve/CVE-2020-11100", }, { category: "external", summary: "SUSE Bug 1168023 for CVE-2020-11100", url: "https://bugzilla.suse.com/1168023", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 8.8, baseSeverity: "HIGH", vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", version: "3.1", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "important", }, ], title: "CVE-2020-11100", }, { cve: "CVE-2021-39240", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2021-39240", }, ], notes: [ { category: "general", text: "An issue was discovered in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3. It does not ensure that the scheme and path portions of a URI have the expected characters. For example, the authority field (as observed on a target HTTP/2 server) might differ from what the routing rules were intended to achieve.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2021-39240", url: "https://www.suse.com/security/cve/CVE-2021-39240", }, { category: "external", summary: "SUSE Bug 1189549 for CVE-2021-39240", url: "https://bugzilla.suse.com/1189549", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", version: "3.1", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "important", }, ], title: "CVE-2021-39240", }, { cve: "CVE-2021-40346", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2021-40346", }, ], notes: [ { category: "general", text: "An integer overflow exists in HAProxy 2.0 through 2.5 in htx_add_header that can be exploited to perform an HTTP request smuggling attack, allowing an attacker to bypass all configured http-request HAProxy ACLs and possibly other ACLs.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, references: [ { category: "external", summary: "CVE-2021-40346", url: "https://www.suse.com/security/cve/CVE-2021-40346", }, { category: "external", summary: "SUSE Bug 1189877 for CVE-2021-40346", url: "https://bugzilla.suse.com/1189877", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", version: "3.1", }, products: [ "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.aarch64", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.ppc64le", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.s390x", "openSUSE Tumbleweed:haproxy-2.4.4+git0.acb1d0bea-1.2.x86_64", ], }, ], threats: [ { category: "impact", date: "2024-06-15T00:00:00Z", details: "important", }, ], title: "CVE-2021-40346", }, ], }
opensuse-su-2019:2555-1
Vulnerability from csaf_opensuse
Published
2019-11-23 19:21
Modified
2019-11-23 19:21
Summary
Security update for haproxy
Notes
Title of the patch
Security update for haproxy
Description of the patch
This update for haproxy to version 2.0.5+git0.d905f49a fixes the following issues:
Security issue fixed:
- CVE-2019-14241: Fixed a cookie memory corruption problem. (bsc#1142529)
The update to 2.0.5 brings lots of features and bugfixes:
- new internal native HTTP representation called HTX, was already in 1.9 and is now enabled by default in 2.0
- end-to-end HTTP/2 support including trailers and continuation frames, as needed for gRPC ; HTTP/2 may also be upgraded from HTTP/1.1 using the H2 preface;
- server connection pooling and more advanced reuse, with ALPN protocol negotiation (already in 1.9)
- layer 7 retries, allowing to use 0-RTT and TCP Fast Open to the servers as well as on the frontend
- much more scalable multi-threading, which is even enabled by default on platforms where it was successfully tested ; by default, as many threads are started as the number of CPUs haproxy is allowed to run on. This removes a lot of configuration burden in VMs and containers
- automatic maxconn setting for the process and the frontends, directly based on the number of available FDs (easier configuration in containers and with systemd)
- logging to stdout for use in containers and systemd (already in 1.9). Logs can now provide micro-second resolution for some events
- peers now support SSL, declaration of multiple stick-tables directly in the peers section, and synchronization of server names, not just IDs
- In master-worker mode, the master process now exposes its own CLI and can communicate with all other processes (including the stopping ones), even allowing to connect to their CLI and check their state. It is also possible to start some sidecar programs and monitor them from the master, and the master can automatically kill old processes that survived too many reloads
- the incoming connections are load-balanced between all threads depending on their load to minimize the processing time and maximize the capacity (already in 1.9)
- the SPOE connection load-balancing was significantly improved in order to reduce high percentiles of SPOA response time (already in 1.9)
- the 'random' load balancing algorithm and a power-of-two-choices variant were introduced
- statistics improvements with per-thread counters for certain things, and a prometheus exporter for all our statistics;
- lots of debugging help, it's easier to produce a core dump, there are new commands on the CLI to control various things, there is a watchdog to fail cleanly when a thread deadlock or a spinning task are detected, so overall it should provide a better experience in field and less round trips between users and developers (hence less stress during an incident).
- all 3 device detection engines are now compatible with multi-threading and can be build-tested without any external dependencies
- 'do-resolve' http-request action to perform a DNS resolution on any, sample, and resolvers now support relying on /etc/resolv.conf to match the local resolver
- log sampling and balancing : it's now possible to send 1 log every 10 to a server, or to spread the logging load over multiple log servers;
- a new SPOA agent (spoa_server) allows to interface haproxy with Python and Lua programs
- support for Solaris' event ports (equivalent of kqueue or epoll) which will significantly improve the performance there when dealing with numerous connections
- some warnings are now reported for some deprecated options that will be removed in 2.1. Since 2.0 is long term supported, there's no emergency to convert them, however if you see these warnings, you need to understand that you're among their extremely rare users and just because of this you may be taking risks by keeping them
- A new SOCKS4 server-side layer was provided ; it allows outgoing connections to be forwarded through a SOCKS4 proxy (such as ssh -D).
- priority- and latency- aware server queues : it is possible now to assign priorities to certain requests and/or to give them a time bonus or penalty to refine control of the traffic and be able to engage on SLAs.
- internally the architecture was significantly redesigned to allow to further improve performance and make it easier to implement protocols that span over multiple layers (such as QUIC). This work started in 1.9 and will continue with 2.1.
- the I/O, applets and tasks now share the same multi-threaded scheduler, giving a much better responsiveness and fairness between all tasks as is visible with the CLI which always responds instantly even under extreme loads (started in 1.9)
- the internal buffers were redesigned to ease zero-copy operations, so that it is possible to sustain a high bandwidth even when forwarding HTTP/1 to/from HTTP/2 (already in 1.9)
This update was imported from the SUSE:SLE-15:Update update project.
Patchnames
openSUSE-2019-2555
Terms of use
CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
{ document: { aggregate_severity: { namespace: "https://www.suse.com/support/security/rating/", text: "moderate", }, category: "csaf_security_advisory", csaf_version: "2.0", distribution: { text: "Copyright 2024 SUSE LLC. All rights reserved.", tlp: { label: "WHITE", url: "https://www.first.org/tlp/", }, }, lang: "en", notes: [ { category: "summary", text: "Security update for haproxy", title: "Title of the patch", }, { category: "description", text: "\n \nThis update for haproxy to version 2.0.5+git0.d905f49a fixes the following issues:\n\nSecurity issue fixed:\n\n- CVE-2019-14241: Fixed a cookie memory corruption problem. (bsc#1142529)\n\nThe update to 2.0.5 brings lots of features and bugfixes:\n\n- new internal native HTTP representation called HTX, was already in 1.9 and is now enabled by default in 2.0\n- end-to-end HTTP/2 support including trailers and continuation frames, as needed for gRPC ; HTTP/2 may also be upgraded from HTTP/1.1 using the H2 preface;\n- server connection pooling and more advanced reuse, with ALPN protocol negotiation (already in 1.9)\n- layer 7 retries, allowing to use 0-RTT and TCP Fast Open to the servers as well as on the frontend\n- much more scalable multi-threading, which is even enabled by default on platforms where it was successfully tested ; by default, as many threads are started as the number of CPUs haproxy is allowed to run on. This removes a lot of configuration burden in VMs and containers\n- automatic maxconn setting for the process and the frontends, directly based on the number of available FDs (easier configuration in containers and with systemd)\n- logging to stdout for use in containers and systemd (already in 1.9). Logs can now provide micro-second resolution for some events\n- peers now support SSL, declaration of multiple stick-tables directly in the peers section, and synchronization of server names, not just IDs\n- In master-worker mode, the master process now exposes its own CLI and can communicate with all other processes (including the stopping ones), even allowing to connect to their CLI and check their state. It is also possible to start some sidecar programs and monitor them from the master, and the master can automatically kill old processes that survived too many reloads\n- the incoming connections are load-balanced between all threads depending on their load to minimize the processing time and maximize the capacity (already in 1.9)\n- the SPOE connection load-balancing was significantly improved in order to reduce high percentiles of SPOA response time (already in 1.9)\n- the 'random' load balancing algorithm and a power-of-two-choices variant were introduced\n- statistics improvements with per-thread counters for certain things, and a prometheus exporter for all our statistics;\n- lots of debugging help, it's easier to produce a core dump, there are new commands on the CLI to control various things, there is a watchdog to fail cleanly when a thread deadlock or a spinning task are detected, so overall it should provide a better experience in field and less round trips between users and developers (hence less stress during an incident).\n- all 3 device detection engines are now compatible with multi-threading and can be build-tested without any external dependencies\n- 'do-resolve' http-request action to perform a DNS resolution on any, sample, and resolvers now support relying on /etc/resolv.conf to match the local resolver\n- log sampling and balancing : it's now possible to send 1 log every 10 to a server, or to spread the logging load over multiple log servers;\n- a new SPOA agent (spoa_server) allows to interface haproxy with Python and Lua programs\n- support for Solaris' event ports (equivalent of kqueue or epoll) which will significantly improve the performance there when dealing with numerous connections\n- some warnings are now reported for some deprecated options that will be removed in 2.1. Since 2.0 is long term supported, there's no emergency to convert them, however if you see these warnings, you need to understand that you're among their extremely rare users and just because of this you may be taking risks by keeping them\n- A new SOCKS4 server-side layer was provided ; it allows outgoing connections to be forwarded through a SOCKS4 proxy (such as ssh -D).\n- priority- and latency- aware server queues : it is possible now to assign priorities to certain requests and/or to give them a time bonus or penalty to refine control of the traffic and be able to engage on SLAs.\n- internally the architecture was significantly redesigned to allow to further improve performance and make it easier to implement protocols that span over multiple layers (such as QUIC). This work started in 1.9 and will continue with 2.1.\n- the I/O, applets and tasks now share the same multi-threaded scheduler, giving a much better responsiveness and fairness between all tasks as is visible with the CLI which always responds instantly even under extreme loads (started in 1.9)\n- the internal buffers were redesigned to ease zero-copy operations, so that it is possible to sustain a high bandwidth even when forwarding HTTP/1 to/from HTTP/2 (already in 1.9)\n\n\nThis update was imported from the SUSE:SLE-15:Update update project.", title: "Description of the patch", }, { category: "details", text: "openSUSE-2019-2555", title: "Patchnames", }, { category: "legal_disclaimer", text: "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).", title: "Terms of use", }, ], publisher: { category: "vendor", contact_details: "https://www.suse.com/support/security/contact/", name: "SUSE Product Security Team", namespace: "https://www.suse.com/", }, references: [ { category: "external", summary: "SUSE ratings", url: "https://www.suse.com/support/security/rating/", }, { category: "self", summary: "URL of this CSAF notice", url: "https://ftp.suse.com/pub/projects/security/csaf/opensuse-su-2019_2555-1.json", }, { category: "self", summary: "URL for openSUSE-SU-2019:2555-1", url: "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/GOCOZCGJIDUANW2OMYVRU77C6CGWQJUF/#GOCOZCGJIDUANW2OMYVRU77C6CGWQJUF", }, { category: "self", summary: "E-Mail link for openSUSE-SU-2019:2555-1", url: "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/GOCOZCGJIDUANW2OMYVRU77C6CGWQJUF/#GOCOZCGJIDUANW2OMYVRU77C6CGWQJUF", }, { category: "self", summary: "SUSE Bug 1142529", url: "https://bugzilla.suse.com/1142529", }, { category: "self", summary: "SUSE CVE CVE-2019-14241 page", url: "https://www.suse.com/security/cve/CVE-2019-14241/", }, ], title: "Security update for haproxy", tracking: { current_release_date: "2019-11-23T19:21:49Z", generator: { date: "2019-11-23T19:21:49Z", engine: { name: "cve-database.git:bin/generate-csaf.pl", version: "1", }, }, id: "openSUSE-SU-2019:2555-1", initial_release_date: "2019-11-23T19:21:49Z", revision_history: [ { date: "2019-11-23T19:21:49Z", number: "1", summary: "Current version", }, ], status: "final", version: "1", }, }, product_tree: { branches: [ { branches: [ { branches: [ { category: "product_version", name: "haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64", product: { name: "haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64", product_id: "haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64", }, }, ], category: "architecture", name: "x86_64", }, { branches: [ { category: "product_name", name: "openSUSE Leap 15.0", product: { name: "openSUSE Leap 15.0", product_id: "openSUSE Leap 15.0", product_identification_helper: { cpe: "cpe:/o:opensuse:leap:15.0", }, }, }, ], category: "product_family", name: "SUSE Linux Enterprise", }, ], category: "vendor", name: "SUSE", }, ], relationships: [ { category: "default_component_of", full_product_name: { name: "haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64 as component of openSUSE Leap 15.0", product_id: "openSUSE Leap 15.0:haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64", }, product_reference: "haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64", relates_to_product_reference: "openSUSE Leap 15.0", }, ], }, vulnerabilities: [ { cve: "CVE-2019-14241", ids: [ { system_name: "SUSE CVE Page", text: "https://www.suse.com/security/cve/CVE-2019-14241", }, ], notes: [ { category: "general", text: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", title: "CVE description", }, ], product_status: { recommended: [ "openSUSE Leap 15.0:haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64", ], }, references: [ { category: "external", summary: "CVE-2019-14241", url: "https://www.suse.com/security/cve/CVE-2019-14241", }, { category: "external", summary: "SUSE Bug 1142529 for CVE-2019-14241", url: "https://bugzilla.suse.com/1142529", }, ], remediations: [ { category: "vendor_fix", details: "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n", product_ids: [ "openSUSE Leap 15.0:haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64", ], }, ], scores: [ { cvss_v3: { baseScore: 7.5, baseSeverity: "HIGH", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, products: [ "openSUSE Leap 15.0:haproxy-2.0.5+git0.d905f49a-lp150.2.13.1.x86_64", ], }, ], threats: [ { category: "impact", date: "2019-11-23T19:21:49Z", details: "important", }, ], title: "CVE-2019-14241", }, ], }
fkie_cve-2019-14241
Vulnerability from fkie_nvd
Published
2019-07-23 13:15
Modified
2024-11-21 04:26
Severity ?
Summary
HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.
References
{ configurations: [ { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*", matchCriteriaId: "188F573A-5FCE-450C-95A3-53F567E1618B", versionEndIncluding: "1.9.8", versionStartIncluding: "1.4", vulnerable: true, }, { criteria: "cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*", matchCriteriaId: "C7F9D8D5-6D60-45C7-9E4D-3A49E5DE731D", versionEndIncluding: "2.0.2", versionStartIncluding: "2.0.0", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, ], cveTags: [], descriptions: [ { lang: "en", value: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", }, { lang: "es", value: "HAProxy hasta versión 2.0.2, permite a los atacantes causar una denegación de servicio (ha_panic) por medio de vectores relacionados con la función htx_manage_client_side_cookies en el archivo proto_htx.c.", }, ], id: "CVE-2019-14241", lastModified: "2024-11-21T04:26:16.597", metrics: { cvssMetricV2: [ { acInsufInfo: false, baseSeverity: "MEDIUM", cvssData: { accessComplexity: "LOW", accessVector: "NETWORK", authentication: "NONE", availabilityImpact: "PARTIAL", baseScore: 5, confidentialityImpact: "NONE", integrityImpact: "NONE", vectorString: "AV:N/AC:L/Au:N/C:N/I:N/A:P", version: "2.0", }, exploitabilityScore: 10, impactScore: 2.9, obtainAllPrivilege: false, obtainOtherPrivilege: false, obtainUserPrivilege: false, source: "nvd@nist.gov", type: "Primary", userInteractionRequired: false, }, ], cvssMetricV30: [ { cvssData: { attackComplexity: "LOW", attackVector: "NETWORK", availabilityImpact: "HIGH", baseScore: 7.5, baseSeverity: "HIGH", confidentialityImpact: "NONE", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "NONE", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, exploitabilityScore: 3.9, impactScore: 3.6, source: "nvd@nist.gov", type: "Primary", }, ], }, published: "2019-07-23T13:15:13.240", references: [ { source: "cve@mitre.org", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html", }, { source: "cve@mitre.org", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html", }, { source: "cve@mitre.org", tags: [ "Third Party Advisory", "VDB Entry", ], url: "http://www.securityfocus.com/bid/109352", }, { source: "cve@mitre.org", tags: [ "Exploit", "Third Party Advisory", ], url: "https://github.com/haproxy/haproxy/issues/181", }, { source: "af854a3a-2127-422b-91ae-364da2661108", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html", }, { source: "af854a3a-2127-422b-91ae-364da2661108", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html", }, { source: "af854a3a-2127-422b-91ae-364da2661108", tags: [ "Third Party Advisory", "VDB Entry", ], url: "http://www.securityfocus.com/bid/109352", }, { source: "af854a3a-2127-422b-91ae-364da2661108", tags: [ "Exploit", "Third Party Advisory", ], url: "https://github.com/haproxy/haproxy/issues/181", }, ], sourceIdentifier: "cve@mitre.org", vulnStatus: "Modified", weaknesses: [ { description: [ { lang: "en", value: "CWE-835", }, ], source: "nvd@nist.gov", type: "Primary", }, ], }
ghsa-rwrj-rg8q-w32h
Vulnerability from github
Published
2022-05-24 16:51
Modified
2022-05-24 16:51
Details
HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.
{ affected: [], aliases: [ "CVE-2019-14241", ], database_specific: { cwe_ids: [], github_reviewed: false, github_reviewed_at: null, nvd_published_at: "2019-07-23T13:15:00Z", severity: "HIGH", }, details: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", id: "GHSA-rwrj-rg8q-w32h", modified: "2022-05-24T16:51:02Z", published: "2022-05-24T16:51:02Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2019-14241", }, { type: "WEB", url: "https://github.com/haproxy/haproxy/issues/181", }, { type: "WEB", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html", }, { type: "WEB", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html", }, { type: "WEB", url: "http://www.securityfocus.com/bid/109352", }, ], schema_version: "1.4.0", severity: [], }
gsd-2019-14241
Vulnerability from gsd
Modified
2023-12-13 01:23
Details
HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.
Aliases
Aliases
{ GSD: { alias: "CVE-2019-14241", description: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", id: "GSD-2019-14241", references: [ "https://www.suse.com/security/cve/CVE-2019-14241.html", ], }, gsd: { metadata: { exploitCode: "unknown", remediation: "unknown", reportConfidence: "confirmed", type: "vulnerability", }, osvSchema: { aliases: [ "CVE-2019-14241", ], details: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", id: "GSD-2019-14241", modified: "2023-12-13T01:23:52.601075Z", schema_version: "1.4.0", }, }, namespaces: { "cve.org": { CVE_data_meta: { ASSIGNER: "cve@mitre.org", ID: "CVE-2019-14241", STATE: "PUBLIC", }, affects: { vendor: { vendor_data: [ { product: { product_data: [ { product_name: "n/a", version: { version_data: [ { version_value: "n/a", }, ], }, }, ], }, vendor_name: "n/a", }, ], }, }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "eng", value: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", }, ], }, problemtype: { problemtype_data: [ { description: [ { lang: "eng", value: "n/a", }, ], }, ], }, references: { reference_data: [ { name: "https://github.com/haproxy/haproxy/issues/181", refsource: "MISC", url: "https://github.com/haproxy/haproxy/issues/181", }, { name: "109352", refsource: "BID", url: "http://www.securityfocus.com/bid/109352", }, { name: "openSUSE-SU-2019:2556", refsource: "SUSE", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html", }, { name: "openSUSE-SU-2019:2555", refsource: "SUSE", url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html", }, ], }, }, "nvd.nist.gov": { configurations: { CVE_data_version: "4.0", nodes: [ { children: [], cpe_match: [ { cpe23Uri: "cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*", cpe_name: [], versionEndIncluding: "1.9.8", versionStartIncluding: "1.4", vulnerable: true, }, { cpe23Uri: "cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*", cpe_name: [], versionEndIncluding: "2.0.2", versionStartIncluding: "2.0.0", vulnerable: true, }, ], operator: "OR", }, ], }, cve: { CVE_data_meta: { ASSIGNER: "cve@mitre.org", ID: "CVE-2019-14241", }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "en", value: "HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in proto_htx.c.", }, ], }, problemtype: { problemtype_data: [ { description: [ { lang: "en", value: "CWE-835", }, ], }, ], }, references: { reference_data: [ { name: "https://github.com/haproxy/haproxy/issues/181", refsource: "MISC", tags: [ "Exploit", "Third Party Advisory", ], url: "https://github.com/haproxy/haproxy/issues/181", }, { name: "109352", refsource: "BID", tags: [ "Third Party Advisory", "VDB Entry", ], url: "http://www.securityfocus.com/bid/109352", }, { name: "openSUSE-SU-2019:2555", refsource: "SUSE", tags: [], url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00060.html", }, { name: "openSUSE-SU-2019:2556", refsource: "SUSE", tags: [], url: "http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00062.html", }, ], }, }, impact: { baseMetricV2: { acInsufInfo: false, cvssV2: { accessComplexity: "LOW", accessVector: "NETWORK", authentication: "NONE", availabilityImpact: "PARTIAL", baseScore: 5, confidentialityImpact: "NONE", integrityImpact: "NONE", vectorString: "AV:N/AC:L/Au:N/C:N/I:N/A:P", version: "2.0", }, exploitabilityScore: 10, impactScore: 2.9, obtainAllPrivilege: false, obtainOtherPrivilege: false, obtainUserPrivilege: false, severity: "MEDIUM", userInteractionRequired: false, }, baseMetricV3: { cvssV3: { attackComplexity: "LOW", attackVector: "NETWORK", availabilityImpact: "HIGH", baseScore: 7.5, baseSeverity: "HIGH", confidentialityImpact: "NONE", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "NONE", vectorString: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.0", }, exploitabilityScore: 3.9, impactScore: 3.6, }, }, lastModifiedDate: "2020-08-24T17:37Z", publishedDate: "2019-07-23T13:15Z", }, }, }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.