Eclipse Basyx Go Components
Monthly
We need to produce a JSON object with specific fields based on all provided data. The key is to synthesize from multiple sources: CVE description, CVSS vector, CWE, EPSS, patch availability, CPE, tags, SSVC, references, EUVD, source code diff. The analysis should be comprehensive. Let's extract and synthesize. Product name: "Eclipse BaSyx Go Components" (3 words: Eclipse BaSyx Go Components, but "Eclipse BaSyx Go Components" is the exact product; "Eclipse BaSyx" might be too generic. "Eclipse BaSyx Go" is 3 words. However, the description says "Eclipse BaSyx Go Components", CPE: eclipse_foundation:eclipse_basyx_go_components. Could be "Eclipse BaSyx Go Components" but that's 4 words. Perhaps "BaSyx Go Components" or "Eclipse BaSyx". The requirement: "1-3 words ONLY. The specific product or service name affected." So "Eclipse BaSyx Go" could be 3 words. Actually "Eclipse BaSyx Go" is three. But the official product might be "Eclipse BaSyx" (the project) but the component is "Go Components". I'll use "Eclipse BaSyx Go" as the product. Now summary: need a 2-3 sentence plain-language summary. Do not copy description. Start with specific impact verb and product. For example: "Authorization bypass in Eclipse BaSyx Go Components ABAC deployments allows unauthenticated remote attackers to access protected API routes by appending trailing slashes." Should mention what the vulnerability is, who affected, what attacker can do. Mention if actively exploited (KEV status: no KEV mentioned, so "no public exploit identified at time of analysis" or "publicly available exploit code exists"? SSVC says Exploitation: poc. So a POC exists. So it's "publicly available exploit code exists". Also EPSS 0.35% low. So summary: "Authorization bypass in Eclipse BaSyx Go Components v1.0.0 and earlier allows unauthenticated remote attackers to bypass Attribute-Based Access Control (ABAC) by appending a trailing slash to API requests, leading to unauthorized read, write, or delete operations on
We need to produce a JSON object with specific fields based on all provided data. The key is to synthesize from multiple sources: CVE description, CVSS vector, CWE, EPSS, patch availability, CPE, tags, SSVC, references, EUVD, source code diff. The analysis should be comprehensive. Let's extract and synthesize. Product name: "Eclipse BaSyx Go Components" (3 words: Eclipse BaSyx Go Components, but "Eclipse BaSyx Go Components" is the exact product; "Eclipse BaSyx" might be too generic. "Eclipse BaSyx Go" is 3 words. However, the description says "Eclipse BaSyx Go Components", CPE: eclipse_foundation:eclipse_basyx_go_components. Could be "Eclipse BaSyx Go Components" but that's 4 words. Perhaps "BaSyx Go Components" or "Eclipse BaSyx". The requirement: "1-3 words ONLY. The specific product or service name affected." So "Eclipse BaSyx Go" could be 3 words. Actually "Eclipse BaSyx Go" is three. But the official product might be "Eclipse BaSyx" (the project) but the component is "Go Components". I'll use "Eclipse BaSyx Go" as the product. Now summary: need a 2-3 sentence plain-language summary. Do not copy description. Start with specific impact verb and product. For example: "Authorization bypass in Eclipse BaSyx Go Components ABAC deployments allows unauthenticated remote attackers to access protected API routes by appending trailing slashes." Should mention what the vulnerability is, who affected, what attacker can do. Mention if actively exploited (KEV status: no KEV mentioned, so "no public exploit identified at time of analysis" or "publicly available exploit code exists"? SSVC says Exploitation: poc. So a POC exists. So it's "publicly available exploit code exists". Also EPSS 0.35% low. So summary: "Authorization bypass in Eclipse BaSyx Go Components v1.0.0 and earlier allows unauthenticated remote attackers to bypass Attribute-Based Access Control (ABAC) by appending a trailing slash to API requests, leading to unauthorized read, write, or delete operations on