Comparison Overview

Oarsport

VS

Body Glove International

Oarsport

Vermont House, Nottingham, Nottinghamshire, NG11 7HQ, GB
Last Update: 2025-11-26
View Profile
Between 750 and 799
http://www.oarsport.co.uk/

Here at Oarsport with our combined vast experience and knowledge of our sport at just about every level, we have used and abused most makes of rowing equipment for over six decades! We know what works and what doesn't. We know what is designed and built well. We know what performs best when you need it most. In our own rowing successes we've relied on the equipment we now distribute among the UK's rowing community. We've had long relationships with the people behind the products. We've seen them grow and develop into the leading rowing equipment manufacturers known and trusted across the globe. We know, we've rowed, trained and coached with the best.

NAICS: None
NAICS Definition:
Employees: 5
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Body Glove International

504 N. Broadway, Redondo Beach, California, 90277, US
Last Update: 2025-11-27
Between 750 and 799
http://www.bodyglove.com/

While 63 years have passed since Bill and Bob Meistrell founded Body Glove, the company still embodies their ambitious spirit of innovation through water sports adventure. Inspired by their legacy, and backed by over 6 decades of quality, we continue to develop innovative products to enhance your comfort, safety and fun both in and out the water. We invite you to join our water sports family and live a life that celebrates All Things Water."

NAICS: None
NAICS Definition: Others
Employees: 62
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/oarsport-limited.jpeg
Oarsport
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/body-glove-international.jpeg
Body Glove International
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Oarsport
100%
Compliance Rate
0/4 Standards Verified
Body Glove International
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Oarsport in 2025.

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Body Glove International in 2025.

Incident History — Oarsport (X = Date, Y = Severity)

Oarsport cyber incidents detection timeline including parent company and subsidiaries

Incident History — Body Glove International (X = Date, Y = Severity)

Body Glove International cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/oarsport-limited.jpeg
Oarsport
Incidents

No Incident

https://images.rankiteo.com/companyimages/body-glove-international.jpeg
Body Glove International
Incidents

No Incident

FAQ

Both Oarsport company and Body Glove International company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Body Glove International company has disclosed a higher number of cyber incidents compared to Oarsport company.

In the current year, Body Glove International company and Oarsport company have not reported any cyber incidents.

Neither Body Glove International company nor Oarsport company has reported experiencing a ransomware attack publicly.

Neither Body Glove International company nor Oarsport company has reported experiencing a data breach publicly.

Neither Body Glove International company nor Oarsport company has reported experiencing targeted cyberattacks publicly.

Neither Oarsport company nor Body Glove International company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oarsport nor Body Glove International holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Oarsport company nor Body Glove International company has publicly disclosed detailed information about the number of their subsidiaries.

Body Glove International company employs more people globally than Oarsport company, reflecting its scale as a Sporting Goods.

Neither Oarsport nor Body Glove International holds SOC 2 Type 1 certification.

Neither Oarsport nor Body Glove International holds SOC 2 Type 2 certification.

Neither Oarsport nor Body Glove International holds ISO 27001 certification.

Neither Oarsport nor Body Glove International holds PCI DSS certification.

Neither Oarsport nor Body Glove International holds HIPAA certification.

Neither Oarsport nor Body Glove International holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References