home.social

#nttdata — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nttdata, aggregated by home.social.

  1. 🚨 CVE-2026-45585 (YellowKey)

    Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey". The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices.
    We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #yellowkey #microsoft #bitlocker #cve202645585

  2. 🚨 CVE-2026-45585 (YellowKey)

    Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey". The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices.
    We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #yellowkey #microsoft #bitlocker #cve202645585

  3. 🚨 CVE-2026-45585 (YellowKey)

    Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey". The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices.
    We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #yellowkey #microsoft #bitlocker #cve202645585

  4. 🚨 CVE-2026-31635 (DirtyDecrypt / DirtyCBC)

    rxrpc: fix oversized RESPONSE authenticator length check

    rxgk_verify_response() decodes auth_len from the packet and is supposed
    to verify that it fits in the remaining bytes. The existing check is
    inverted, so oversized RESPONSE authenticators are accepted and passed
    to rxgk_decrypt_skb(), which can later reach skb_to_sgvec() with an
    impossible length and hit BUG_ON(len).

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #dirtydecrypt #dirtycbc #linux #kernel #lpe #cve202631635

  5. 🚨 CVE-2026-31635 (DirtyDecrypt / DirtyCBC)

    rxrpc: fix oversized RESPONSE authenticator length check

    rxgk_verify_response() decodes auth_len from the packet and is supposed
    to verify that it fits in the remaining bytes. The existing check is
    inverted, so oversized RESPONSE authenticators are accepted and passed
    to rxgk_decrypt_skb(), which can later reach skb_to_sgvec() with an
    impossible length and hit BUG_ON(len).

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #dirtydecrypt #dirtycbc #linux #kernel #lpe # cve202631635

  6. 🚨 CVE-2026-42945 (NGINX Rift)

    NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_rewrite_module module. This vulnerability exists when the rewrite directive is followed by a rewrite, if, or set directive and an unnamed Perl-Compatible Regular Expression (PCRE) capture (for example, $1, $2) with a replacement string that includes a question mark (?). An unauthenticated attacker along with conditions beyond its control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, for systems with Address Space Layout Randomization (ASLR ) disabled, code execution is possible. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #nginxrift #cve202642945 #nginx

  7. 🚨 CVE-2026-42945 (NGINX Rift)

    NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_rewrite_module module. This vulnerability exists when the rewrite directive is followed by a rewrite, if, or set directive and an unnamed Perl-Compatible Regular Expression (PCRE) capture (for example, $1, $2) with a replacement string that includes a question mark (?). An unauthenticated attacker along with conditions beyond its control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, for systems with Address Space Layout Randomization (ASLR ) disabled, code execution is possible. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #nginxrift #cve202642945 #nginx

  8. 🚨 CVE-2026-46333 (ssh-keysign-pwn)

    In the Linux kernel, the following vulnerability has been resolved:

    ptrace: slightly saner 'get_dumpable()' logic

    The 'dumpability' of a task is fundamentally about the memory image of
    the task - the concept comes from whether it can core dump or not - and
    makes no sense when you don't have an associated mm.

    And almost all users do in fact use it only for the case where the task
    has a mm pointer.

    But we have one odd special case: ptrace_may_access() uses 'dumpable' to
    check various other things entirely independently of the MM (typically
    explicitly using flags like PTRACE_MODE_READ_FSCREDS). Including for
    threads that no longer have a VM (and maybe never did, like most kernel
    threads).

    It's not what this flag was designed for, but it is what it is.

    The ptrace code does check that the uid/gid matches, so you do have to
    be uid-0 to see kernel thread details, but this means that the
    traditional "drop capabilities" model doesn't make any difference for
    this all.

    Make it all make a bit more sense by saying that if you don't have a
    MM pointer, we'll use a cached "last dumpability" flag if the thread
    ever had a MM (it will be zero for kernel threads since it is never
    set), and require a proper CAP_SYS_PTRACE capability to override.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #sshkeysignpwn #cve202646333 #linux #kernel

  9. 🚨 CVE-2026-46333 (ssh-keysign-pwn)

    In the Linux kernel, the following vulnerability has been resolved:

    ptrace: slightly saner 'get_dumpable()' logic

    The 'dumpability' of a task is fundamentally about the memory image of
    the task - the concept comes from whether it can core dump or not - and
    makes no sense when you don't have an associated mm.

    And almost all users do in fact use it only for the case where the task
    has a mm pointer.

    But we have one odd special case: ptrace_may_access() uses 'dumpable' to
    check various other things entirely independently of the MM (typically
    explicitly using flags like PTRACE_MODE_READ_FSCREDS). Including for
    threads that no longer have a VM (and maybe never did, like most kernel
    threads).

    It's not what this flag was designed for, but it is what it is.

    The ptrace code does check that the uid/gid matches, so you do have to
    be uid-0 to see kernel thread details, but this means that the
    traditional "drop capabilities" model doesn't make any difference for
    this all.

    Make it all make a bit more sense by saying that if you don't have a
    MM pointer, we'll use a cached "last dumpability" flag if the thread
    ever had a MM (it will be zero for kernel threads since it is never
    set), and require a proper CAP_SYS_PTRACE capability to override.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #sshkeysignpwn #cve202646333 #linux #kernel

  10. 🚨 CVE-2026-46333 (ssh-keysign-pwn)

    In the Linux kernel, the following vulnerability has been resolved:

    ptrace: slightly saner 'get_dumpable()' logic

    The 'dumpability' of a task is fundamentally about the memory image of
    the task - the concept comes from whether it can core dump or not - and
    makes no sense when you don't have an associated mm.

    And almost all users do in fact use it only for the case where the task
    has a mm pointer.

    But we have one odd special case: ptrace_may_access() uses 'dumpable' to
    check various other things entirely independently of the MM (typically
    explicitly using flags like PTRACE_MODE_READ_FSCREDS). Including for
    threads that no longer have a VM (and maybe never did, like most kernel
    threads).

    It's not what this flag was designed for, but it is what it is.

    The ptrace code does check that the uid/gid matches, so you do have to
    be uid-0 to see kernel thread details, but this means that the
    traditional "drop capabilities" model doesn't make any difference for
    this all.

    Make it all make a bit more sense by saying that if you don't have a
    MM pointer, we'll use a cached "last dumpability" flag if the thread
    ever had a MM (it will be zero for kernel threads since it is never
    set), and require a proper CAP_SYS_PTRACE capability to override.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #sshkeysignpwn #cve202646333 #linux #kernel

  11. 🚨 CVE-2026-45185 (Dead.Letter)

    Exim before 4.99.3, in certain GnuTLS configurations, has a remotely reachable use-after-free in the BDAT body parsing path. It is triggered when a client sends a TLS close_notify mid-body during a CHUNKING transfer, followed by a final cleartext byte on the same TCP connection. This can lead to heap corruption. An unauthenticated network attacker exploiting this vulnerability could execute arbitrary code.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #deadletter #cve202645185 #exim #gnutls

  12. 🚨 CVE-2026-45185 (Dead.Letter)

    Exim before 4.99.3, in certain GnuTLS configurations, has a remotely reachable use-after-free in the BDAT body parsing path. It is triggered when a client sends a TLS close_notify mid-body during a CHUNKING transfer, followed by a final cleartext byte on the same TCP connection. This can lead to heap corruption. An unauthenticated network attacker exploiting this vulnerability could execute arbitrary code.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #deadletter #cve202645185 #exim #gnutls

  13. 🚨 CVE-2026-45185 (Dead.Letter)

    Exim before 4.99.3, in certain GnuTLS configurations, has a remotely reachable use-after-free in the BDAT body parsing path. It is triggered when a client sends a TLS close_notify mid-body during a CHUNKING transfer, followed by a final cleartext byte on the same TCP connection. This can lead to heap corruption. An unauthenticated network attacker exploiting this vulnerability could execute arbitrary code.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #deadletter #cve202645185 #exim #gnutls

  14. 🚨 CVE-2026-41651 (Pack2TheRoot)

    PackageKit vulnerable to TOCTOU Race on Transaction Flags leads to arbitrary package installation as root

    PackageKit is a a D-Bus abstraction layer that allows the user to manage packages in a secure way using a cross-distro, cross-architecture API. PackageKit between and including versions 1.0.2 and 1.3.4 is vulnerable to a time-of-check time-of-use (TOCTOU) race condition on transaction flags that allows unprivileged users to install packages as root and thus leads to a local privilege escalation. This is patched in version 1.3.5.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #pack2theroot #cve2026411651 #packagekit #toctou

  15. 🚨 CVE-2026-41651 (Pack2TheRoot)

    PackageKit vulnerable to TOCTOU Race on Transaction Flags leads to arbitrary package installation as root

    PackageKit is a a D-Bus abstraction layer that allows the user to manage packages in a secure way using a cross-distro, cross-architecture API. PackageKit between and including versions 1.0.2 and 1.3.4 is vulnerable to a time-of-check time-of-use (TOCTOU) race condition on transaction flags that allows unprivileged users to install packages as root and thus leads to a local privilege escalation. This is patched in version 1.3.5.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #pack2theroot #cve2026411651 #packagekit #toctou

  16. 🚨 CVE-2026-41651 (Pack2TheRoot)

    PackageKit vulnerable to TOCTOU Race on Transaction Flags leads to arbitrary package installation as root

    PackageKit is a a D-Bus abstraction layer that allows the user to manage packages in a secure way using a cross-distro, cross-architecture API. PackageKit between and including versions 1.0.2 and 1.3.4 is vulnerable to a time-of-check time-of-use (TOCTOU) race condition on transaction flags that allows unprivileged users to install packages as root and thus leads to a local privilege escalation. This is patched in version 1.3.5.

    ℹ️ Additional info on ZEN SecDB secdb.nttzen.cloud/cve/detail/

    #nttdata #zen #secdb #infosec
    #pack2theroot #cve2026411651 #packagekit #toctou

  17. NTT Global Data Centers, the world's third-largest data center provider outside of China, is working to double its capacity to meet the rising demand for the critical digital infrastructure amid an AI boom. japantimes.co.jp/business/2026 #business #companies #nttdata #ai

  18. NTT Data to boost India headcount by 5,000 this year: The Japanese IT services firm is hiring across software programming, consulting and IT support, with large US00M+ contracts doubling in the past year. The company employs 40,000 in India and is building four data centers as part of a US.5B investment. economictimes.indiatimes.com/t #India #Tech #NTTData

  19. 🚨 CVE-2026-21858 - Ni8mare

    n8n is an open source workflow automation platform. Versions below 1.121.0 enable an attacker to access files on the underlying server through execution of certain form-based workflows. A vulnerable workflow could grant access to an unauthenticated remote attacker, resulting in exposure of sensitive information stored on the system and may enable further compromise depending on deployment configuration and workflow usage. This issue is fixed in version 1.121.0.

    secdb.nttzen.cloud/cve/detail/

    #SecDB #InfoSec #n8n #Ni8mare #CVE #CVE202621858 #NTTDATA #CyberSecurity

  20. 🚨 CVE-2026-21858 - Ni8mare

    n8n is an open source workflow automation platform. Versions below 1.121.0 enable an attacker to access files on the underlying server through execution of certain form-based workflows. A vulnerable workflow could grant access to an unauthenticated remote attacker, resulting in exposure of sensitive information stored on the system and may enable further compromise depending on deployment configuration and workflow usage. This issue is fixed in version 1.121.0.

    secdb.nttzen.cloud/cve/detail/

    #SecDB #InfoSec #n8n #Ni8mare #CVE #CVE202621858 #NTTDATA #CyberSecurity

  21. NTT Data Group is considering building data centers in Saudi Arabia as the Japanese firm looks to capitalize on fresh momentum around artificial intelligence in the kingdom. japantimes.co.jp/business/2025 #business #companies #nttdata #saudiarabia #ai #tech

  22. Nippon Telegraph and Telephone plans to buy back as much as ¥200 billion ($1.4 billion) of its shares in a move the telecom operator says is geared toward raising capital efficiency and boosting shareholder returns. japantimes.co.jp/business/2025 #business #companies #nttdata #ntt #acquisitions

  23. NTT plans to make its AI powerhouse NTT Data Group a wholly owned subsidiary in a deal worth ¥2.37 trillion ($16.5 billion), the latest in a series of Japanese parent companies absorbing their listed units. japantimes.co.jp/business/2025 #business #ntt #nttdata #acquisitions

  24. The Daiei supermarket chain has opened Japan's first store where shoppers can walk out with their groceries as an app automatically collects payment, replacing cash registers with a network of cameras and weight sensors. japantimes.co.jp/business/2023 #business #tech #retailers #daiei #amazongo #nttdata #yokohama

  25. The Daiei supermarket chain has opened Japan's first store where shoppers can walk out with their groceries as an app automatically collects payment, replacing cash registers with a network of cameras and weight sensors. japantimes.co.jp/business/2023 #business #tech #retailers #daiei #amazongo #nttdata #yokohama