Skip to main content
assistive.skiplink.to.breadcrumbs
assistive.skiplink.to.header.menu
assistive.skiplink.to.action.menu
assistive.skiplink.to.quick.search
Log in
Confluence
Spaces
Hit enter to search
Help
Online Help
Keyboard Shortcuts
Feed Builder
What’s new
Available Gadgets
About Confluence
Log in
Android
Pages
Boards
Space shortcuts
Dashboard
Secure Coding Home
Android
C
C++
Java
Perl
Page tree
Browse pages
Configure
Space tools
View Page
A
t
tachments (0)
Page History
Page Information
View in Hierarchy
View Source
Export to PDF
Export to Word
Pages
…
Android Secure Coding Standard
4 By Language
C Coding Language
Applicable in Principle to Android (C Rules/Recomendations)
Page Information
Title:
Applicable in Principle to Android (C Rules/Recomendations)
Author:
Unknown User (lflynn)
Apr 03, 2014
Last Changed by:
Sandy Shrum
May 07, 2015
Tiny Link:
(useful for email)
https://wiki.sei.cmu.edu/confluence/x/GdAxBQ
Export As:
Word
·
PDF
Incoming Links
Android (1)
Page:
How to Change Applicability When a Rules and Recommendations Change
Hierarchy
Parent Page
Page:
C Coding Language
Labels
Global Labels (2)
applicability-list
c
Recent Changes
Time
Editor
May 07, 2015 14:12
Sandy Shrum
View Changes
May 07, 2015 11:47
Sandy Shrum
View Changes
May 07, 2015 09:49
Sandy Shrum
View Changes
May 06, 2015 07:38
Barbara White
View Changes
May 06, 2015 07:38
Sandy Shrum
View Page History
Outgoing Links
External Links (3)
stackoverflow.com/questions/7245550/android
https://www.securecoding.cert.org/confluence/display/seccod…
developer.android.com/guide/practices/verifying-apps-art.ht…
SEI CERT C Coding Standard (26)
Page:
SIG35-C. Do not return from a computational exception signal handler
Page:
SIG02-C. Avoid using signals to implement normal functionality
Page:
FLP04-C. Check floating-point inputs for exceptional values
Page:
FLP05-C. Do not use denormalized numbers
Page:
SIG31-C. Do not access shared objects in signal handlers
Page:
API02-C. Functions that read or write to or from an array should take an argument to specify the source or target size
Page:
SIG01-C. Understand implementation-specific details regarding signal handler persistence
Page:
STR11-C. Do not specify the bound of a character array initialized with a string literal
Page:
API05-C. Use conformant array parameters
Page:
INT35-C. Use correct integer precisions
Page:
FLP34-C. Ensure that floating-point conversions are within range of the new type
Page:
EXP36-C. Do not cast pointers into more strictly aligned pointer types
Page:
FLP36-C. Preserve precision when converting integral values to floating-point type
Page:
STR30-C. Do not attempt to modify string literals
Page:
FIO47-C. Use valid format strings
Page:
STR31-C. Guarantee that storage for strings has sufficient space for character data and the null terminator
Page:
SIG00-C. Mask signals handled by noninterruptible signal handlers
Page:
SIG30-C. Call only asynchronous-safe functions within signal handlers
Page:
MEM33-C. Allocate and copy structures containing a flexible array member dynamically
Page:
MSC19-C. For functions that return an array, prefer returning an empty array over a null value
Page:
FLP07-C. Cast the return value of a function that returns a floating-point type
Page:
FIO30-C. Exclude user input from format strings
Page:
DCL38-C. Use the correct syntax when declaring a flexible array member
Page:
FLP06-C. Convert integers to floating point for floating-point operations
Page:
SIG34-C. Do not call signal() from within interruptible signal handlers
Page:
FLP32-C. Prevent or detect domain and range errors in math functions
Overview
Content Tools
{"serverDuration": 85, "requestCorrelationId": "14167b2c67a18243"}