Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
: - http://www.securitytracker.com/id/1042071 - https://github.com/krb5/krb5/commit/e1caf6fb74981da62039846931ebdffed71309d1 - https://access.redhat.com/errata/RHSA-2018:3071 - https://bugzilla.redhat.com/show_bug.cgi?id=1551082 - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OIFUL3CPM4S5TOXTTOCQ3CUZN6XCXUTR/ - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891869 - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GK5T6JPMBHBPKS7HNGHYUUF4KKRMNSNU/ - https://lists.debian.org/debian-lts-announce/2019/01/msg00020.html - https://access.redhat.com/errata/RHBA-2019:0327 - https://lists.debian.org/
/debian-lts-announce/2019/01/msg00020.html - https://access.redhat.com/errata/RHBA-2019:0327 - https://lists.debian.org/debian-lts-announce/2021/09/msg00019.html
CVE ID: CVE-2018-5731 State: PUBLISHED Published: 2018-03-22T16:00:00 Last Updated: 2024-08-05T05:40:51.268Z Vendors: n/a Products: n/a Problem Types: n/a Description: An issue was discovered in Heimdal PRO 2.2.190. As part of the scanning feature, a process called md.hs writes an executable called CS1.tmp to C:\windows\TEMP. Afterwards the executable is run. It is possible for an attacker to create the file first, let md.hs overwrite it, and then rewrite the file in the window between md.hs closing the file and executing it. This can be exploited via opportunistic locks and a high priority thread. The vulnerability is triggered when a scan starts. NOTE: any affected Heimdal products are com
d a high priority thread. The vulnerability is triggered when a scan starts. NOTE: any affected Heimdal products are completely unrelated to the Heimdal vendor of a Kerberos 5 product on the h5l.org web site. Additional Analyst Notes: - CVE Program Container: References: - https://improsec.com/blog/heimdal-advisory-2
CVE ID: CVE-2018-5732 State: PUBLISHED Published: 2019-10-09T14:17:14.251822Z Last Updated: 2024-09-16T18:19:36.136Z Severity: HIGH (CVSS 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: ISC Products: ISC DHCP Problem Types: Affected versions of dhclient should crash due to an out-of-bounds memory access if they receive and process a triggering response packet. However, buffer overflow outcomes can vary by operating system, and outcomes such as remote code execution may be possible in some circumstances. Where they are present, operating system mitigation strategies such as address space layout randomization (ASLR) should make it difficult to leverage this vulnerability to achieve
es such as address space layout randomization (ASLR) should make it difficult to leverage this vulnerability to achieve remote code execution, but we cannot rule it out as impossible. The safest course is to patch dhclient so that the buffer overflow cannot occur. Description: Failure to properly bounds-check a buffer used for processing DHCP options allows a malicious server (or an entity masquerading as a server) to cause a buffer overflow (and resulting crash) in dhclient by sending a response containing a specially constructed options section. Affects ISC DHCP versions 4.1.0 -> 4.1-ESV-R15, 4.2.0 -> 4.2.8, 4.3.0 -> 4.3.6, 4.4.0 Additional Analyst Notes: - CVE Program Container: Reference
4.1.0 -> 4.1-ESV-R15, 4.2.0 -> 4.2.8, 4.3.0 -> 4.3.6, 4.4.0 Additional Analyst Notes: - CVE Program Container: References: - https://kb.isc.org/docs/aa-01565
CVE ID: CVE-2018-5733 State: PUBLISHED Published: 2019-01-16T20:00:00.000Z Last Updated: 2025-04-25T23:02:52.084Z Severity: MEDIUM (CVSS 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: ISC Products: ISC DHCP Problem Types: Successful exploitation of this vulnerability may exhaust the memory available to dhcpd and/or cause it to crash, resulting in a denial of service to clients. Description: A malicious client which is allowed to send very large amounts of traffic (billions of packets) to a DHCP server can eventually overflow a 32-bit reference counter, potentially causing dhcpd to crash. Affects ISC DHCP 4.1.0 -> 4.1-ESV-R15, 4.2.0 -> 4.2.8, 4.3.0 -> 4.3.6, 4.4.0. Additional Anal
ly causing dhcpd to crash. Affects ISC DHCP 4.1.0 -> 4.1-ESV-R15, 4.2.0 -> 4.2.8, 4.3.0 -> 4.3.6, 4.4.0. Additional Analyst Notes: - CVE Program Container: References: - https://kb.isc.org/docs/aa-01567 - https://access.redhat.com/errata/RHSA-2018:0469 - https://www.debian.org/security/2018/dsa-4133 - https://usn.ubuntu.com/3586-2/ - https://access.redhat.com/errata/RHSA-2018:0483 - https://usn.ubuntu.com/3586-1/ - http://www.securityfocus.com/bid/103188 - http://www.securitytracker.com/id/1040437 - https://lists.debian.org/debian-lts-announce/2018/03/msg00015.html
CVE ID: CVE-2018-5734 State: PUBLISHED Published: 2019-01-16T20:00:00Z Last Updated: 2024-09-17T02:31:46.321Z Severity: HIGH (CVSS 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: ISC Products: BIND 9 Problem Types: Servers running the affected versions (9.10.5-S1 to 9.10.5-S4, 9.10.6-S1, and 9.10.6-S2) are vulnerable if they allow recursion, unless the SERVFAIL cache is disabled for the receiving view. Description: While handling a particular type of malformed packet BIND erroneously selects a SERVFAIL rcode instead of a FORMERR rcode. If the receiving view has the SERVFAIL cache feature enabled, this can trigger an assertion failure in badcache.c when the request doesn't contain
he SERVFAIL cache feature enabled, this can trigger an assertion failure in badcache.c when the request doesn't contain all of the expected information. Affects BIND 9.10.5-S1 to 9.10.5-S4, 9.10.6-S1, 9.10.6-S2. Additional Analyst Notes: - CVE Program Container: References: - https://kb.isc.org/docs/aa-01562 - https://security.netapp.com/advisory/ntap-20180926-0005/ - http://www.securityfocus.com/bid/103189 - http://www.securitytracker.com/id/1040438
CVE ID: CVE-2018-5735 State: PUBLISHED Published: 2019-10-30T13:42:57.183131Z Last Updated: 2024-09-16T17:58:19.116Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: Debian Products: BIND9 Problem Types: The Debian backport of the fix for CVE-2017-3137 leads to assertion failure in validator.c:1858 Description: The Debian backport of the fix for CVE-2017-3137 leads to assertion failure in validator.c:1858; Affects Debian versions 9.9.5.dfsg-9+deb8u15; 9.9.5.dfsg-9+deb8u18; 9.10.3.dfsg.P4-12.3+deb9u5; 9.11.5.P4+dfsg-5.1 No ISC releases are affected. Other packages from other distributions who did similar backports for the fix for 2017-3137 may also be affected.
cted. Other packages from other distributions who did similar backports for the fix for 2017-3137 may also be affected. Additional Analyst Notes: - CVE Program Container: References: - https://security-tracker.debian.org/tracker/CVE-2018-5735
CVE ID: CVE-2018-5736 State: PUBLISHED Published: 2019-01-16T20:00:00 Last Updated: 2024-08-05T05:40:51.229Z Vendors: n/a Products: n/a Problem Types: n/a Description: An error in zone database reference counting can lead to an assertion failure if a server which is running an affected version of BIND attempts several transfers of a slave zone in quick succession. This defect could be deliberately exercised by an attacker who is permitted to cause a vulnerable server to initiate zone transfers (for example: by sending valid NOTIFY messages), causing the named process to exit after failing the assertion test. Affects BIND 9.12.0 and 9.12.1. Additional Analyst Notes: - CVE Program Container: R
t after failing the assertion test. Affects BIND 9.12.0 and 9.12.1. Additional Analyst Notes: - CVE Program Container: References: - http://www.securityfocus.com/bid/104386 - http://www.securitytracker.com/id/1040941 - https://security.netapp.com/advisory/ntap-20180926-0004/ - https://kb.isc.org/docs/aa-01602
CVE ID: CVE-2018-5737 State: PUBLISHED Published: 2019-01-16T20:00:00Z Last Updated: 2024-09-16T22:40:22.628Z Severity: MEDIUM (CVSS 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: ISC Products: BIND 9 Problem Types: Servers running a vulnerable version of BIND (9.12.0, 9.12.1) which permit recursion to clients and which have the max-stale-ttl parameter set to a non-zero value are at risk. Description: A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cas
ditionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1. Additional Analyst Notes: - CVE Program Container: References: - http://www.securityfocus.com/bid/104236 - https://kb.isc.org/docs/aa-01606 - http://www.securitytracker.com/id/1040942 - https://security.netapp.com/advisory/ntap-20180926-0004/
CVE ID: CVE-2018-5738 State: PUBLISHED Published: 2019-01-16T20:00:00Z Last Updated: 2024-09-16T22:20:36.711Z Severity: MEDIUM (CVSS 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Vendors: ISC Products: BIND 9 Problem Types: There are several potential problems which can be caused by improperly permitting recursive service to unauthorized clients, including: Additional queries from unauthorized clients may increase the load on a server, possibly degrading service to authorized clients. Allowing queries from unauthorized clients can potentially allow a server to be co-opted for use in DNS reflection attacks. An attacker may be able to deduce which queries a server has previously serviced b
ed for use in DNS reflection attacks. An attacker may be able to deduce which queries a server has previously serviced by examining the results of queries answered from the cache, potentially leaking private information about what queries have been performed. Description: Change #4777 (introduced in October 2017) introduced an unforeseen issue in releases which were issued after that date, affecting which clients are permitted to make recursive queries to a BIND nameserver. The intended (and documented) behavior is that if an operator has not specified a value for the "allow-recursion" setting, it SHOULD default to one of the following: none, if "recursion no;" is set in named.conf; a value
w-recursion" setting, it SHOULD default to one of the following: none, if "recursion no;" is set in named.conf; a value inherited from the "allow-query-cache" or "allow-query" settings IF "recursion yes;" (the default for that setting) AND match lists are explicitly set for "allow-query-cache" or "allow-query" (see the BIND9 Administrative Reference Manual section 6.2 for more details); or the intended default of "allow-recursion {localhost; localnets;};" if "recursion yes;" is in effect and no values are explicitly set for "allow-query-cache" or "allow-query". However, because of the regression introduced by change #4777, it is possible when "recursion yes;" is in effect and no match list v
ause of the regression introduced by change #4777, it is possible when "recursion yes;" is in effect and no match list values are provided for "allow-query-cache" or "allow-query" for the setting of "allow-recursion" to inherit a setting of all hosts from the "allow-query" setting default, improperly permitting recursion to all clients. Affects BIND 9.9.12, 9.10.7, 9.11.3, 9.12.0->9.12.1-P2, the development release 9.13.0, and also releases 9.9.12-S1, 9.10.7-S1, 9.11.3-S1, and 9.11.3-S2 from BIND 9 Supported Preview Edition. Additional Analyst Notes: - CVE Program Container: References: - https://usn.ubuntu.com/3683-1/ - https://kb.isc.org/docs/aa-01616 - http://www.securitytracker.com/id/10
: References: - https://usn.ubuntu.com/3683-1/ - https://kb.isc.org/docs/aa-01616 - http://www.securitytracker.com/id/1041115 - https://security.gentoo.org/glsa/201903-13 - https://security.netapp.com/advisory/ntap-20190830-0002/
CVE ID: CVE-2018-5739 State: PUBLISHED Published: 2019-01-16T20:00:00Z Last Updated: 2024-09-17T02:11:49.386Z Severity: MEDIUM (CVSS 6.5 CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: ISC Products: Kea DHCP Problem Types: Only servers using hooks which make use of the callout handle store are affected. A Kea server which is using one or more hooks libraries that exhibit this problem will increase its memory use over time, with the rate of increase being proportional to the amount of DHCP traffic processed. Eventually, due to uncontrolled growth, the server will either exhaust all system memory or, if the administrator has set a per-process memory limit, will hit that limit, after whi
er exhaust all system memory or, if the administrator has set a per-process memory limit, will hit that limit, after which point further memory allocations will fail and the Kea server will crash. An attacker who is within the broadcast domain of the Kea server or in a network which is permitted to relay DHCP traffic to the Kea server can hasten the arrival of this outcome by deliberately sending a large volume of requests to the Kea server. Ability to deliberately trigger this vulnerability depends on the hooks libraries used and the hook points used for callouts. Our scoring for this vulnerability is based on the hook points used for hook libraries distributed by ISC and also based on the
ing for this vulnerability is based on the hook points used for hook libraries distributed by ISC and also based on the assumption that the Kea server does not accept arbitrary traffic from the internet (but is protected, e.g. by firewall, and only accepts DHCP traffic from the local broadcast domain and from nearby networks via authorized DHCP relay agents.) We cannot score every combination, but the risk could be higher to custom-developed hook libraries using other hook points or to servers which accept arbitrary DHCP traffic without restriction. Description: An extension to hooks capabilities which debuted in Kea 1.4.0 introduced a memory leak for operators who are using certain hooks li
n to hooks capabilities which debuted in Kea 1.4.0 introduced a memory leak for operators who are using certain hooks library facilities. In order to support multiple requests simultaneously, Kea 1.4 added a callout handle store but unfortunately the initial implementation of this store does not properly free memory in every case. Hooks which make use of query4 or query6 parameters in their callouts can leak memory, resulting in the eventual exhaustion of available memory and subsequent failure of the server process. Affects Kea DHCP 1.4.0. Additional Analyst Notes: - CVE Program Container: References: - https://kb.isc.org/docs/aa-01626
CVE ID: CVE-2018-5740 State: PUBLISHED Published: 2019-01-16T20:00:00Z Last Updated: 2024-09-16T17:58:43.029Z Severity: HIGH (CVSS 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: ISC Products: BIND 9 Problem Types: Accidental or deliberate triggering of this defect will cause a REQUIRE assertion failure in named, causing the named process to stop execution and resulting in denial of service to clients., Accidental or deliberate triggering of this defect will cause a REQUIRE assertion failure in named, causing the named process to stop execution and resulting in denial of service to clients. Only servers which have explicitly enabled the "deny-answer-aliases" feature are at risk an
enial of service to clients. Only servers which have explicitly enabled the "deny-answer-aliases" feature are at risk and disabling the feature prevents exploitation. Description: "deny-answer-aliases" is a little-used feature intended to help recursive server operators protect end users against DNS rebinding attacks, a potential method of circumventing the security model used by client browsers. However, a defect in this feature makes it easy, when the feature is in use, to experience an assertion failure in name.c. Affects BIND 9.7.0->9.8.8, 9.9.0->9.9.13, 9.10.0->9.10.8, 9.11.0->9.11.4, 9.12.0->9.12.2, 9.13.0->9.13.2. Additional Analyst Notes: - CVE Program Container: References: - http:/
9.11.0->9.11.4, 9.12.0->9.12.2, 9.13.0->9.13.2. Additional Analyst Notes: - CVE Program Container: References: - http://www.securityfocus.com/bid/105055 - https://lists.debian.org/debian-lts-announce/2018/08/msg00033.html - https://access.redhat.com/errata/RHSA-2018:2570 - https://access.redhat.com/errata/RHSA-2018:2571 - https://usn.ubuntu.com/3769-2/ - http://www.securitytracker.com/id/1041436 - https://security.netapp.com/advisory/ntap-20180926-0003/ - https://kb.isc.org/docs/aa-01639 - https://usn.ubuntu.com/3769-1/ - https://security.gentoo.org/glsa/201903-13 - http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00027.html - http://lists.opensuse.org/opensuse-security-annou
/lists.opensuse.org/opensuse-security-announce/2019-06/msg00027.html - http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00026.html - https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux03927en_us - https://lists.debian.org/debian-lts-announce/2021/11/msg00001.html
CVE ID: CVE-2018-5741 State: PUBLISHED Published: 2019-01-16T20:00:00Z Last Updated: 2024-09-17T02:26:39.095Z Severity: MEDIUM (CVSS 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) Vendors: ISC Products: BIND 9 Problem Types: The krb5-subdomain and ms-subdomain update policy rule types permit updates from any client authenticated with a valid Kerberos or Windows machine principal from the REALM specified in the identity field, to modify records in the zone at or below the name specified in the name field. The incorrect documentation, however, indicated that the policy would be restricted to names at or below the machine's name as encoded in the Windows or Kerberos principal. For example, i
ld be restricted to names at or below the machine's name as encoded in the Windows or Kerberos principal. For example, if named.conf contains the following configuration statement in the zone "example.com": zone example.com { ... update-policy { grant SUB.EXAMPLE.COM krb5-subdomain . ANY; }; }; ...then a client possessing a valid Kerberos machine principal for host/machine.sub.example.com@SUB.EXAMPLE.COM would be allowed to update any record at or below "example.com", whereas the documentation indicated that updates would only be permitted at or below "machine.sub.example.com". In practice, the name of the machine encoded in the principal is not checked to ensure that it matches the records
om". In practice, the name of the machine encoded in the principal is not checked to ensure that it matches the records to be updated. The update policy for the zone, having established that the client possesses a valid machine principal from the SUB.EXAMPLE.COM realm, simply allows updates to all records within the zone "example.com". The ms-subdomain rule type behaves similarly, but for Windows machine principals such as machine$@SUB.EXAMPLE.COM instead of Kerberos principals. The krb5-subdomain and ms-subdomain rules are intended to limit updates to names below the name field (in this example, ".", which covers the entire zone). Because of a separate bug in the named.conf parser, a name f
field (in this example, ".", which covers the entire zone). Because of a separate bug in the named.conf parser, a name field below "." could not be configured in some releases. Maintenance releases of BIND released during or after October 2018 (9.11.5 or higher, 9.12.3 or higher) will address this configuration bug, as well as adding new krb5-selfsub and ms-selfsub rule types which more accurately implement the behavior that the ARM formerly attributed to krb5-subdomain and ms-subdomain. Description: To provide fine-grained controls over the ability to use Dynamic DNS (DDNS) to update records in a zone, BIND 9 provides a feature called update-policy. Various rules can be configured to limit
) to update records in a zone, BIND 9 provides a feature called update-policy. Various rules can be configured to limit the types of updates that can be performed by a client, depending on the key used when sending the update request. Unfortunately, some rule types were not initially documented, and when documentation for them was added to the Administrator Reference Manual (ARM) in change #3112, the language that was added to the ARM at that time incorrectly described the behavior of two rule types, krb5-subdomain and ms-subdomain. This incorrect documentation could mislead operators into believing that policies they had configured were more restrictive than they actually were. This affects
d operators into believing that policies they had configured were more restrictive than they actually were. This affects BIND versions prior to BIND 9.11.5 and BIND 9.12.3. Additional Analyst Notes: - CVE Program Container: References: - http://www.securityfocus.com/bid/105379 - http://www.securitytracker.com/id/1041674 - https://kb.isc.org/docs/cve-2018-5741 - https://security.gentoo.org/glsa/201903-13 - https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux03927en_us - https://access.redhat.com/errata/RHSA-2019:2057 - https://security.netapp.com/advisory/ntap-20190830-0001/ - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00041.html - http://l
com/advisory/ntap-20190830-0001/ - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00041.html - http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00044.html
CVE ID: CVE-2018-5742 State: PUBLISHED Published: 2019-10-30T13:43:12.526427Z Last Updated: 2024-09-17T03:53:09.481Z Severity: MEDIUM (CVSS 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: RedHat Products: BIND9 Problem Types: An oversight by RedHat while backporting a feature leads to an assertion failure in buffer.c:420 Description: While backporting a feature for a newer branch of BIND9, RedHat introduced a path leading to an assertion failure in buffer.c:420. Affects RedHat versions bind-9.9.4-65.el7 -> bind-9.9.4-72.el7. No ISC releases are affected. Other packages from other distributions who made the same error may also be affected. Additional Analyst Notes: - CVE Program Co
ckages from other distributions who made the same error may also be affected. Additional Analyst Notes: - CVE Program Container: References: - https://access.redhat.com/security/cve/cve-2018-5742
CVE ID: CVE-2018-5743 State: PUBLISHED Published: 2019-10-09T14:17:14.293079Z Last Updated: 2024-09-17T02:26:38.493Z Severity: HIGH (CVSS 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: ISC Products: BIND 9 Problem Types: By exploiting the failure to limit simultaneous TCP connections, an attacker can deliberately exhaust the pool of file descriptors available to named, potentially affecting network connections and the management of files such as log files or zone journal files. In cases where the named process is not limited by OS-enforced per-process limits, this could additionally potentially lead to exhaustion of all available free file descriptors on that system. Description:
is could additionally potentially lead to exhaustion of all available free file descriptors on that system. Description: By design, BIND is intended to limit the number of TCP clients that can be connected at any given time. The number of allowed connections is a tunable parameter which, if unset, defaults to a conservative value for most servers. Unfortunately, the code which was intended to limit the number of simultaneous connections contained an error which could be exploited to grow the number of simultaneous connections beyond this limit. Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.6, 9.12.0 -> 9.12.4, 9.14.0. BIND 9 Supported Preview Edition versions 9.9.3-S1 -> 9.11.5-