MSA A.I CyberSecurity Scoring
27/10/2025
Access Monitoring Plan
Access Monitoring Plan
No incidents recorded for MSD Saúde Animal in 2026.
No incidents recorded for MSD Saúde Animal in 2026.
No incidents recorded for MSD Saúde Animal in 2026.
A leader in veterinary care, VCA Animal Hospitals is committed to taking care of the future of veterinary medicine. We are a family of hometown animal hospitals determined to positively impact pets, people and our communities. From general practice to emergency and specialty care, VCA delivers world-class medicine and hometown care to more than four million pets each year. We invest in cutting-edge tools, training and technology that enable Associates across our national network of hospitals to lead the industry today and into tomorrow. Among our talented 35,000 Associates are nearly 7,000 veterinarians – including 430 who are board-certified specialists – nearly 4,000 credentialed technicians and over 10,000 veterinary assistants – all dedicated to giving pets the very best in medical care. As part of the Mars Veterinary Health family of brands, VCA is taking care of the future of veterinary medicine to help achieve the Mars Petcare Purpose—A Better World for Pets™. To learn more about VCA, visit: www.vca.com or find us on Facebook, Instagram, Twitter and LinkedIn. https://bit.ly/vcaprivacy https://bit.ly/vcalegal
Banfield Pet Hospital was founded in Portland, Ore. in 1955 and today is a pioneer in preventive veterinary care with more than 1,000 general veterinary hospitals in 42 states, Washington D.C., Puerto Rico, and Mexico. Every year, Banfield’s veterinary teams provide high-quality veterinary care to over three million pets, including more than 2 million Optimum Wellness Plan clients. As part of the Mars Veterinary Health family of practices, Banfield’s more than 19,000 Associates nationwide are committed to positively impacting society through the Banfield Gives Back program and advancing veterinary medicine in service of our purpose — A BETTER WORLD FOR PETS® — because pets make a better world for us. Please visit jobs.banfield.com to learn more about joining Banfield’s team of passionate pet health care providers. Page subject to mars.com/legal & mars.com/privacy. Mars is not responsible for content or activity made available via 3rd party sites/services.
Latest updates, reports, and threat intel affecting the global network.
Klever-Go is the Go implementation of the Klever blockchain protocol. Versions from 1.7.14 through 1.7.17 are vulnerable to a remotely triggerable denial of service. Both REST APIs are started with the Gin Engine.Run convenience method, which serves requests through Go's default HTTP server with no ReadHeaderTimeout, ReadTimeout, or MaxHeaderBytes configured. As a result, incoming connections that never complete their request headers are held open indefinitely. When a REST listener is reachable beyond localhost through the documented all-interface bind or a Docker port-publish deployment, a single unauthenticated client can open many slow-header connections and hold them open until server file descriptors are exhausted, preventing the API from accepting new connections. This renders the REST API unavailable to legitimate clients. This issue is fixed in version 1.7.18.
Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttler, or bound on the number of concurrent in-flight spawns. Because the antiflood check runs inside the spawned goroutine rather than before it, a single connected peer can open a direct-send stream and send a stream of well-formed messages to force unbounded goroutine creation, where each goroutine allocates its own stack and holds a message reference until processing completes, adding scheduler and garbage-collection pressure faster than the runtime can drain it. This lets one peer degrade the node's availability and its ability to process legitimate traffic, resulting in a remotely triggerable denial of service. The issue is fixed in 1.7.18.
Klever-Go is the Go implementation of the Klever blockchain protocol. Versions 1.7.14 through 1.7.17 are vulnerable to a nil-pointer panic triggered by a protobuf Transaction whose embedded RawData sub-message is omitted. This omission causes RawData to decode to nil. Every transaction gossiped on the Klever-Go P2P network is decoded and validated synchronously inside the libp2p pubsub topic-validator callback, where txVersionChecker.CheckTxVersion dereferences tx.RawData.Version with no nil check. Because the libp2p pubsub callback, the underlying go-libp2p-pubsub validation worker, and Klever's own network/p2p layer install no recover(), the panic propagates and crashes the entire node process. The attacker payload is a 3-byte protobuf message; no validator key, stake, funds, or on-chain account is required, and delivery aimed at enough of the BLS validator set can halt block production, resulting in a chain halt. This issue has been fixed in version 1.7.18.
Klever-Go is the Go implementation of the Klever blockchain protocol. In versions prior to 1.7.18, the account-data trie syncers are vulnerable to a resource-exhaustion flaw that leaks bounded throttler slots on error paths. In syncDataTrie() (in both userAccountsSyncer.go and kappAccountsSyncer.go), StartProcessing() reserves a slot from the NumGoRoutinesThrottler, but the corresponding EndProcessing() is only called on the success path and on the duplicate-root early return. As a result, any error from trie.NewTrie(), trie.NewTrieSyncer(), or trieSyncer.StartSyncing() (including the network-dependent timeout path) permanently consumes one slot for the lifetime of the throttler. An attacker who can repeatedly cause trie-node sync failures or timeouts during bootstrap can exhaust the bounded throttler, after which further account-data trie syncs stop making progress and SyncAccounts() returns a timeout. Because epoch bootstrap in syncUserAccountsState() and syncKappAccountsState() aborts on any such error, this causes bootstrap to fail, a core availability issue affecting fresh, restarting, or resyncing nodes and validators. This issue is fixed in version 1.7.18.
Ruby LSP is an implementation of the language server protocol for Ruby. Several workspace-level settings in the Ruby LSP VS Code extension prior to version 0.10.4 could override the path to the Ruby executable, the version manager executables, or the Bundler `Gemfile` used at startup. A malicious repository containing a `.vscode/settings.json` could set these values to attacker-controlled targets. Opening and trusting the repository would then execute code with the privileges of the developer. The Ruby LSP gem and clients of the language server in other editors are not affected. Version 0.10.4 of the Ruby LSP VS Code extension fixes the issue.
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.