Barnowl develops a focused real-time location and asset-tracking platform where its vulnerability disclosures center on input-handling and memory-management weaknesses in the core product. The observed weakness classes—improper input validation and buffer-boundary violations—reflect the parsing and data-processing demands of location-tracking systems; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Barnowl over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2010-2725HIGH BarnOwl before 1.6.2 does not check the return code of calls to the (1) ZPending and (2) ZReceiveNotice functions in libzephyr, which allows remote attackers to cause a denial of s | Aug 5, 2010 | 7.5 | 23 | NO | NO |
CVE-2010-0793HIGH Buffer overflow in BarnOwl before 1.5.1 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted CC: header. | Mar 16, 2010 | 7.5 | 23 | NO | NO |
CVE-2009-0363HIGH Multiple buffer overflows in (a) BarnOwl before 1.0.5 and (b) owl 2.1.11 allow remote attackers to execute arbitrary code via vectors involving (1) a crafted zcrypt message, relate | Feb 17, 2009 | 7.5 | 20 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Barnowl.
Media articles that mention a CVE ID that affects a product developed by Barnowl — matched by CVE ID, not by vendor name.