Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CWE VIEW:Weaknesses in Software Written in Verilog
ID:BOSS-249
Vulnerability Mapping:Prohibited
Type:Implicit
Status:Draft
DetailsContent HistoryObserved CVE ExamplesReports
▼Objective

This view (slice) covers issues that are found in Verilog programs that are not common to all languages.

▼Memberships
NatureMappingTypeIDName
HasMemberAllowedB1221Incorrect Register Defaults or Module Parameters
HasMemberAllowedB1223Race Condition for Write-Once Attributes
HasMemberAllowedB1224Improper Restriction of Write-Once Bit Fields
HasMemberAllowedB1251Mirrored Regions with Different Values
HasMemberAllowedB1269Product Released in Non-Release Configuration
HasMemberAllowedB1272Sensitive Information Uncleared Before Debug/Power State Transition
HasMemberAllowedB1273Device Unlock Credential Sharing
HasMemberAllowedB1279Cryptographic Operations are run Before Supporting Units are Ready
HasMemberAllowedB1280Access Control Check Implemented After Asset is Accessed
HasMemberAllowedB1296Incorrect Chaining or Granularity of Debug Components
HasMemberAllowedB1297Unprotected Confidential Information on Device is Accessible by OSAT Vendors
HasMemberAllowedB1298Hardware Logic Contains Race Conditions
HasMemberAllowedB1311Improper Translation of Security Attributes by Fabric Bridge
HasMemberAllowedB1429Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface
HasMemberAllowed-with-ReviewC327Use of a Broken or Risky Cryptographic Algorithm
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1221
Name: Incorrect Register Defaults or Module Parameters
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1223
Name: Race Condition for Write-Once Attributes
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1224
Name: Improper Restriction of Write-Once Bit Fields
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1251
Name: Mirrored Regions with Different Values
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1269
Name: Product Released in Non-Release Configuration
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1272
Name: Sensitive Information Uncleared Before Debug/Power State Transition
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1273
Name: Device Unlock Credential Sharing
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1279
Name: Cryptographic Operations are run Before Supporting Units are Ready
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1280
Name: Access Control Check Implemented After Asset is Accessed
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1296
Name: Incorrect Chaining or Granularity of Debug Components
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1297
Name: Unprotected Confidential Information on Device is Accessible by OSAT Vendors
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1298
Name: Hardware Logic Contains Race Conditions
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1311
Name: Improper Translation of Security Attributes by Fabric Bridge
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 1429
Name: Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface
Nature: HasMember
Mapping: Allowed-with-Review
Type: Class
ID: 327
Name: Use of a Broken or Risky Cryptographic Algorithm
▼Vendors
Note: CVE records are filtered based on below selected vendors.
Not available
▼Vulnerability Mapping Notes
Usage:Prohibited
Reason:View
Rationale:

This entry is a View. Views are not weaknesses and therefore inappropriate to describe the root causes of vulnerabilities.

Comments:

Use this View or other Views to search and navigate for the appropriate weakness.

▼Notes
▼Audience
StakeholderDescription
▼References
Expand AllCollapse All
BOSS-249 - Weaknesses in Software Written in Verilog
Details not found