Statements (119)
| Predicate | Object |
|---|---|
| gptkbp:instance_of |
gptkb:Common_Weakness_Enumeration
|
| gptkbp:bfsLayer |
6
|
| gptkbp:bfsParent |
gptkb:CWE-74
|
| gptkbp:affects |
Software applications
|
| gptkbp:associated_with |
Data integrity issues.
Performance issues. Security vulnerabilities. |
| gptkbp:category |
Numeric Errors
|
| gptkbp:consequences |
Unexpected behavior.
|
| gptkbp:created_by |
gptkb:MITRE
|
| gptkbp:difficulty |
gptkb:tank
|
| gptkbp:discovered_by |
Legacy systems
|
| gptkbp:example |
A user inputs a large number that is truncated.
Converting a large integer to a byte. |
| gptkbp:first_published |
2021-09-01
|
| gptkbp:has_weakness |
gptkb:CWE-190
CWE-682 |
| https://www.w3.org/2000/01/rdf-schema#label |
CWE-197
|
| gptkbp:impact |
Data loss
Incorrect calculations |
| gptkbp:is_described_as |
The software does not properly handle numeric values that are truncated when converted to a smaller data type.
|
| gptkbp:is_often_used_in |
Embedded systems.
Data processing applications. Financial applications. |
| gptkbp:is_protected_by |
Implement range checks.
Code reviews. Static analysis tools. Use appropriate data types. |
| gptkbp:is_referenced_in |
https://cwe.mitre.org/data/definitions/197.html
|
| gptkbp:name |
Numeric Truncation Error
|
| gptkbp:related_to |
gptkb:CWE-190
CWE-682 |
| gptkbp:released |
Use automated testing tools.
Implement proper error handling. Avoid type casting. Conduct peer reviews. Conduct regular audits. Conduct scenario-based training. Conduct thorough testing. Conduct training on numeric issues. Create a checklist for numeric handling. Create a knowledge base. Create a mentorship program. Create a numeric handling checklist. Create a numeric handling community. Create a numeric handling framework. Create a numeric handling guide. Create a numeric handling policy. Create a numeric handling strategy. Create a numeric handling toolkit. Document data type choices. Document lessons learned. Educate developers on numeric types. Encourage collaboration with academia. Encourage continuous improvement. Encourage continuous learning. Encourage cross-team collaboration. Encourage feedback on numeric handling. Encourage innovation in numeric handling. Encourage open communication. Encourage open discussions on numeric issues. Encourage participation in conferences. Encourage participation in forums. Encourage participation in hackathons. Encourage participation in open-source projects. Encourage participation in research projects. Encourage participation in study groups. Encourage participation in webinars. Encourage participation in workshops. Encourage rapid prototyping. Encourage transparency in numeric handling. Engage in knowledge sharing. Engage with experts. Establish a feedback loop. Establish a review process for numeric changes. Establish coding standards. Foster a culture of accountability. Foster a proactive approach to numeric issues. Foster collaboration among teams. Implement boundary testing. Implement continuous integration. Implement logging for numeric operations. Monitor production systems. Participate in forums. Promote a culture of experimentation. Promote a culture of innovation. Promote a culture of learning. Promote a culture of quality. Promote a culture of respect. Promote a culture of sharing. Promote a culture of trust. Promote best practices. Refactor code for clarity. Review legacy code. Review third-party libraries. Share knowledge within teams. Support research on numeric issues. Use a larger data type. Use assertions in critical code paths. Use assertions to check values. Use code linters. Use libraries that handle large numbers. Use pair programming. Use type-safe languages. Use version control for changes. Utilize agile methodologies. Utilize case studies. Utilize cloud resources. Utilize community resources. Utilize industry standards. Utilize mentorship programs. Utilize metrics to track improvements. Utilize online resources. Utilize peer reviews. Utilize simulation tools. Validate input data. Implement a rewards system for quality improvements. |
| gptkbp:status |
Active
|
| gptkbp:type |
Weakness
|