{"course":{"productid":24031,"modality":6,"active":true,"language":"en","title":"Secure Coding in C and C++","productcode":"SECC-CCPP","vendorcode":"CY","vendorname":"Cydrill","fullproductcode":"CY-SECC-CCPP","courseware":{"has_ekit":false,"has_printkit":true,"language":""},"url":"https:\/\/portal.flane.ch\/course\/cydrill-secc-ccpp","objective":"<ul>\n<li>Getting familiar with essential cyber security concepts<\/li><li>Identify vulnerabilities and their consequences<\/li><li>Learn the security best practices in C and C++<\/li><li>Input validation approaches and principles<\/li><\/ul>","essentials":"<p>General C\/C++ development<\/p>","audience":"<p>C\/C++ developers<\/p>","contents":"<ul>\n<li>Cyber security basics<\/li><li>Buffer overflow<\/li><li>Memory management hardening<\/li><li>Common software security weaknesses<\/li><li>Wrap up<\/li><\/ul>","outline":"<p><strong>DAY 1 <\/strong><\/p>\n<p><strong>Cyber security basics<\/strong>\n<\/p>\n<ul>\n<li>What is security?<\/li><li>Threat and risk<\/li><li>Cyber security threat types<\/li><li>Consequences of insecure software\n<ul>\n<li>Constraints and the market<\/li><li>The dark side<\/li><\/ul><\/li><\/ul><p><strong>Buffer overflow<\/strong>\n<\/p>\n<ul>\n<li>Assembly basics and calling conventions\n<ul>\n<li>x64 assembly essentials<\/li><li>Registers and addressing<\/li><li>Most common instructions<\/li><li>Calling conventions on x64\n<ul>\n<li>Calling convention &ndash; what it is all about<\/li><li>The stack frame<\/li><li>Stacked function calls<\/li><\/ul><\/li><\/ul><\/li><li>Memory management vulnerabilities\n<ul>\n<li>Memory management and security<\/li><li>Vulnerabilities in the real world<\/li><li>Buffer security issues<\/li><li>Buffer overflow on the stack\n<ul>\n<li>Buffer overflow on the stack &ndash; stack smashing<\/li><li>Exploitation &ndash; Hijacking the control flow<\/li><li>Lab &ndash; Buffer overflow 101, code reuse<\/li><li>Exploitation &ndash; Arbitrary code execution<\/li><li>Injecting shellcode<\/li><li>Lab &ndash; Code injection, exploitation with shellcode<\/li><\/ul><\/li><li>Buffer overflow on the heap\n<ul>\n<li>Unsafe unlinking<\/li><li>Case study &ndash; Heartbleed<\/li><\/ul><\/li><li>Pointer manipulation\n<ul>\n<li>Modification of jump tables<\/li><li>Overwriting function pointers<\/li><\/ul><\/li><\/ul><\/li><li>Best practices and some typical mistakes\n<ul>\n<li>Unsafe functions<\/li><li>Dealing with unsafe functions<\/li><li>Lab &ndash; Fixing buffer overflow<\/li><li>What&rsquo;s the problem with asctime()?<\/li><li>Lab &ndash; The problem with asctime()<\/li><li>Using std::string in C++<\/li><li>Unterminated strings<\/li><li>readlink() and string termination<\/li><li>Manipulating C-style strings in C++<\/li><li>Malicious string termination<\/li><li>Lab &ndash; String termination confusion<\/li><li>String length calculation mistakes<\/li><li>Off-by-one errors<\/li><li>Allocating nothing<\/li><\/ul><\/li><\/ul><p><strong>DAY 2<\/strong><\/p>\n<p><strong>Memory management hardening<\/strong>\n<\/p>\n<ul>\n<li>Securing the toolchain\n<ul>\n<li>Securing the toolchain in C and C++<\/li><li>Compiler warnings and security<\/li><li>Using FORTIFY_SOURCE<\/li><li>Lab &ndash; Effects of FORTIFY<\/li><li>AddressSanitizer (ASan)\n<ul>\n<li>Using AddressSanitizer (ASan)<\/li><li>ASan changes to the prologue<\/li><li>ASan changes to memory read\/write operations<\/li><li>ASan changes to the epilogue<\/li><li>Lab &ndash; Using AddressSanitizer<\/li><\/ul><\/li><li>Stack smashing protection\n<ul>\n<li>Detecting BoF with a stack canary<\/li><li>Argument cloning<\/li><li>Stack smashing protection on various platforms<\/li><li>SSP changes to the prologue and epilogue<\/li><li>Lab &ndash; Effects of stack smashing protection<\/li><\/ul><\/li><li>Address Space Layout Randomization (ASLR)\n<ul>\n<li>ASLR on various platforms<\/li><li>Lab &ndash; Effects of ASLR<\/li><li>Circumventing ASLR &ndash; NOP sleds<\/li><\/ul><\/li><li>Non-executable memory areas\n<ul>\n<li>The NX bit<\/li><li>Write XOR Execute (W^X)<\/li><li>NX on various platforms<\/li><li>Lab &ndash; Effects of NX<\/li><li>NX circumvention &ndash; Code reuse attacks\n<ul>\n<li>Return-to-libc \/ arc injection<\/li><\/ul><\/li><li>Return Oriented Programming (ROP)\n<ul>\n<li>Protection against ROP<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>Common software security weaknesses<\/strong>\n<\/p>\n<ul>\n<li>Security features\n<ul>\n<li>Authentication\n<ul>\n<li>Authentication basics<\/li><li>Multi-factor authentication<\/li><li>Authentication weaknesses &ndash; spoofing<\/li><li>Case study &ndash; PayPal 2FA bypass<\/li><\/ul><\/li><li>Password management\n<ul>\n<li>Inbound password management\n<ul>\n<li>Storing account passwords<\/li><li>Password in transit<\/li><li>Lab &ndash; Is just hashing passwords enough?<\/li><li>Dictionary attacks and brute forcing<\/li><li>Salting<\/li><li>Adaptive hash functions for password storage<\/li><li>Password policy\n<ul>\n<li>NIST authenticator requirements for memorized secrets<\/li><\/ul><\/li><li>Case study &ndash; The Ashley Madison data breach\n<ul>\n<li>The dictionary attack<\/li><li>The ultimate crack<\/li><li>Exploitation and the lessons learned<\/li><\/ul><\/li><li>Password database migration<\/li><\/ul><\/li><li>Outbound password management\n<ul>\n<li>Hard coded passwords<\/li><li>Best practices<\/li><li>Lab &ndash; Hardcoded password<\/li><li>Protecting sensitive information in memory\n<ul>\n<li>Challenges in protecting memory<\/li><li>Heap inspection<\/li><li>Compiler optimization challenges<\/li><li>Lab &ndash; Zeroization challenges<\/li><li>Sensitive info in non-locked memory<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><li>Code quality\n<ul>\n<li>Data handling\n<ul>\n<li>Type mismatch<\/li><li>Lab &ndash; Type mismatch<\/li><li>Initialization and cleanup\n<ul>\n<li>Constructors and destructors<\/li><li>Initialization of static objects<\/li><li>Lab &ndash; Initialization cycles<\/li><li>Array disposal in C++<\/li><li>Lab &ndash; Mixing delete and delete[]<\/li><\/ul><\/li><\/ul><\/li><li>Memory and pointers\n<ul>\n<li>Memory and pointer issues<\/li><li>Pointer handling pitfalls<\/li><li>Pointer usage in C and C++\n<ul>\n<li>Use after free<\/li><li>Lab &ndash; Use after free<\/li><li>Lab &ndash; Runtime instrumentation<\/li><li>Double free<\/li><li>Memory leak<\/li><li>Smart pointers and RAII<\/li><li>Smart pointer challenges<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><p><strong>DAY 3<\/strong><\/p>\n<p><strong>Common software security weaknesses<\/strong>\n<\/p>\n<ul>\n<li>Input validation\n<ul>\n<li>Input validation principles\n<ul>\n<li>Blacklists and whitelists<\/li><li>Data validation techniques<\/li><li>What to validate &ndash; the attack surface<\/li><li>Where to validate &ndash; defense in depth<\/li><li>How to validate &ndash; validation vs transformations<\/li><li>Validation with regex<\/li><\/ul><\/li><li>Injection\n<ul>\n<li>Injection principles<\/li><li>Injection attacks<\/li><li>Code injection\n<ul>\n<li>OS command injection\n<ul>\n<li>Lab &ndash; Command injection<\/li><li>OS command injection best practices<\/li><li>Avoiding command injection with the right APIs<\/li><li>Lab &ndash; Command injection best practices<\/li><li>Case study &ndash; Shellshock<\/li><li>Lab &ndash; Shellshock<\/li><\/ul><\/li><li>Process control &ndash; library injection\n<ul>\n<li>DLL hijacking<\/li><li>Lab &ndash; DLL hijacking<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><li>Integer handling problems\n<ul>\n<li>Representing signed numbers<\/li><li>Integer visualization<\/li><li>Integer promotion<\/li><li>Integer overflow<\/li><li>Lab &ndash; Integer overflow<\/li><li>Signed \/ unsigned confusion<\/li><li>Case study &ndash; The Stockholm Stock Exchange<\/li><li>Lab &ndash; Signed \/ unsigned confusion<\/li><li>Integer truncation<\/li><li>Lab &ndash; Integer truncation<\/li><li>Case study &ndash; WannaCry<\/li><li>Best practices\n<ul>\n<li>Upcasting<\/li><li>Precondition testing<\/li><li>Postcondition testing<\/li><li>Using big integer libraries<\/li><li>Best practices in C<\/li><li>UBSan changes to arithmetics<\/li><li>Lab &ndash; Handling integer overflow on the toolchain level in C\/C++<\/li><li>Best practices in C++<\/li><li>Lab &ndash; Integer handling best practices in C++<\/li><\/ul><\/li><\/ul><\/li><li>Files and streams\n<ul>\n<li>Path traversal<\/li><li>Path traversal-related examples<\/li><li>Lab &ndash; Path traversal<\/li><li>Path traversal best practices<\/li><li>Lab &ndash; Path canonicalization<\/li><\/ul><\/li><li>Format string issues\n<ul>\n<li>The problem with printf()<\/li><li>Lab &ndash; Exploiting format string<\/li><\/ul><\/li><\/ul><\/li><li>Time and state\n<ul>\n<li>Race conditions\n<ul>\n<li>File race condition\n<ul>\n<li>Time of check to time of usage &ndash; TOCTTOU<\/li><li>Lab &ndash; TOCTTOU<\/li><li>Insecure temporary file<\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li><\/ul><p>\n<strong>Wrap up<\/strong>\n<\/p>\n<ul>\n<li>Secure coding principles\n<ul>\n<li>Principles of robust programming by Matt Bishop<\/li><li>Secure design principles of Saltzer and Schr&ouml;der<\/li><\/ul><\/li><li>And now what?\n<ul>\n<li>Software security sources and further reading<\/li><li>C and C++ resources<\/li><\/ul><\/li><\/ul>","summary":"<p>Your application written in C and C++ works as intended, so you are done, right? But did you consider feeding in incorrect values? 16Gbs of data? A null? An apostrophe? Negative numbers, or specifically -1 or -231? Because that&rsquo;s what the bad guys will do &ndash; and the list is far from complete.<\/p>\n<p>Handling security needs a healthy level of paranoia, and this is what this course provides: a strong emotional engagement by lots of hands on labs and stories from real life, all to substantially improve code hygiene. Mistakes, consequences, and best practices are our blood, sweat and tears.<\/p>\n<p>All this is put in the context of C and C++, and extended by core programming issues, discussing security pitfalls of these languages.<\/p>\n<p>So that you are prepared for the forces of the dark side.<\/p>\n<p>So that nothing unexpected happens.<\/p>\n<p>Nothing.<\/p>","objective_plain":"- Getting familiar with essential cyber security concepts\n- Identify vulnerabilities and their consequences\n- Learn the security best practices in C and C++\n- Input validation approaches and principles","essentials_plain":"General C\/C++ development","audience_plain":"C\/C++ developers","contents_plain":"- Cyber security basics\n- Buffer overflow\n- Memory management hardening\n- Common software security weaknesses\n- Wrap up","outline_plain":"DAY 1 \n\nCyber security basics\n\n\n\n- What is security?\n- Threat and risk\n- Cyber security threat types\n- Consequences of insecure software\n\n- Constraints and the market\n- The dark side\nBuffer overflow\n\n\n\n- Assembly basics and calling conventions\n\n- x64 assembly essentials\n- Registers and addressing\n- Most common instructions\n- Calling conventions on x64\n\n- Calling convention \u2013 what it is all about\n- The stack frame\n- Stacked function calls\n- Memory management vulnerabilities\n\n- Memory management and security\n- Vulnerabilities in the real world\n- Buffer security issues\n- Buffer overflow on the stack\n\n- Buffer overflow on the stack \u2013 stack smashing\n- Exploitation \u2013 Hijacking the control flow\n- Lab \u2013 Buffer overflow 101, code reuse\n- Exploitation \u2013 Arbitrary code execution\n- Injecting shellcode\n- Lab \u2013 Code injection, exploitation with shellcode\n- Buffer overflow on the heap\n\n- Unsafe unlinking\n- Case study \u2013 Heartbleed\n- Pointer manipulation\n\n- Modification of jump tables\n- Overwriting function pointers\n- Best practices and some typical mistakes\n\n- Unsafe functions\n- Dealing with unsafe functions\n- Lab \u2013 Fixing buffer overflow\n- What\u2019s the problem with asctime()?\n- Lab \u2013 The problem with asctime()\n- Using std::string in C++\n- Unterminated strings\n- readlink() and string termination\n- Manipulating C-style strings in C++\n- Malicious string termination\n- Lab \u2013 String termination confusion\n- String length calculation mistakes\n- Off-by-one errors\n- Allocating nothing\nDAY 2\n\nMemory management hardening\n\n\n\n- Securing the toolchain\n\n- Securing the toolchain in C and C++\n- Compiler warnings and security\n- Using FORTIFY_SOURCE\n- Lab \u2013 Effects of FORTIFY\n- AddressSanitizer (ASan)\n\n- Using AddressSanitizer (ASan)\n- ASan changes to the prologue\n- ASan changes to memory read\/write operations\n- ASan changes to the epilogue\n- Lab \u2013 Using AddressSanitizer\n- Stack smashing protection\n\n- Detecting BoF with a stack canary\n- Argument cloning\n- Stack smashing protection on various platforms\n- SSP changes to the prologue and epilogue\n- Lab \u2013 Effects of stack smashing protection\n- Address Space Layout Randomization (ASLR)\n\n- ASLR on various platforms\n- Lab \u2013 Effects of ASLR\n- Circumventing ASLR \u2013 NOP sleds\n- Non-executable memory areas\n\n- The NX bit\n- Write XOR Execute (W^X)\n- NX on various platforms\n- Lab \u2013 Effects of NX\n- NX circumvention \u2013 Code reuse attacks\n\n- Return-to-libc \/ arc injection\n- Return Oriented Programming (ROP)\n\n- Protection against ROP\nCommon software security weaknesses\n\n\n\n- Security features\n\n- Authentication\n\n- Authentication basics\n- Multi-factor authentication\n- Authentication weaknesses \u2013 spoofing\n- Case study \u2013 PayPal 2FA bypass\n- Password management\n\n- Inbound password management\n\n- Storing account passwords\n- Password in transit\n- Lab \u2013 Is just hashing passwords enough?\n- Dictionary attacks and brute forcing\n- Salting\n- Adaptive hash functions for password storage\n- Password policy\n\n- NIST authenticator requirements for memorized secrets\n- Case study \u2013 The Ashley Madison data breach\n\n- The dictionary attack\n- The ultimate crack\n- Exploitation and the lessons learned\n- Password database migration\n- Outbound password management\n\n- Hard coded passwords\n- Best practices\n- Lab \u2013 Hardcoded password\n- Protecting sensitive information in memory\n\n- Challenges in protecting memory\n- Heap inspection\n- Compiler optimization challenges\n- Lab \u2013 Zeroization challenges\n- Sensitive info in non-locked memory\n- Code quality\n\n- Data handling\n\n- Type mismatch\n- Lab \u2013 Type mismatch\n- Initialization and cleanup\n\n- Constructors and destructors\n- Initialization of static objects\n- Lab \u2013 Initialization cycles\n- Array disposal in C++\n- Lab \u2013 Mixing delete and delete[]\n- Memory and pointers\n\n- Memory and pointer issues\n- Pointer handling pitfalls\n- Pointer usage in C and C++\n\n- Use after free\n- Lab \u2013 Use after free\n- Lab \u2013 Runtime instrumentation\n- Double free\n- Memory leak\n- Smart pointers and RAII\n- Smart pointer challenges\nDAY 3\n\nCommon software security weaknesses\n\n\n\n- Input validation\n\n- Input validation principles\n\n- Blacklists and whitelists\n- Data validation techniques\n- What to validate \u2013 the attack surface\n- Where to validate \u2013 defense in depth\n- How to validate \u2013 validation vs transformations\n- Validation with regex\n- Injection\n\n- Injection principles\n- Injection attacks\n- Code injection\n\n- OS command injection\n\n- Lab \u2013 Command injection\n- OS command injection best practices\n- Avoiding command injection with the right APIs\n- Lab \u2013 Command injection best practices\n- Case study \u2013 Shellshock\n- Lab \u2013 Shellshock\n- Process control \u2013 library injection\n\n- DLL hijacking\n- Lab \u2013 DLL hijacking\n- Integer handling problems\n\n- Representing signed numbers\n- Integer visualization\n- Integer promotion\n- Integer overflow\n- Lab \u2013 Integer overflow\n- Signed \/ unsigned confusion\n- Case study \u2013 The Stockholm Stock Exchange\n- Lab \u2013 Signed \/ unsigned confusion\n- Integer truncation\n- Lab \u2013 Integer truncation\n- Case study \u2013 WannaCry\n- Best practices\n\n- Upcasting\n- Precondition testing\n- Postcondition testing\n- Using big integer libraries\n- Best practices in C\n- UBSan changes to arithmetics\n- Lab \u2013 Handling integer overflow on the toolchain level in C\/C++\n- Best practices in C++\n- Lab \u2013 Integer handling best practices in C++\n- Files and streams\n\n- Path traversal\n- Path traversal-related examples\n- Lab \u2013 Path traversal\n- Path traversal best practices\n- Lab \u2013 Path canonicalization\n- Format string issues\n\n- The problem with printf()\n- Lab \u2013 Exploiting format string\n- Time and state\n\n- Race conditions\n\n- File race condition\n\n- Time of check to time of usage \u2013 TOCTTOU\n- Lab \u2013 TOCTTOU\n- Insecure temporary file\n\nWrap up\n\n\n\n- Secure coding principles\n\n- Principles of robust programming by Matt Bishop\n- Secure design principles of Saltzer and Schr\u00f6der\n- And now what?\n\n- Software security sources and further reading\n- C and C++ resources","summary_plain":"Your application written in C and C++ works as intended, so you are done, right? But did you consider feeding in incorrect values? 16Gbs of data? A null? An apostrophe? Negative numbers, or specifically -1 or -231? Because that\u2019s what the bad guys will do \u2013 and the list is far from complete.\n\nHandling security needs a healthy level of paranoia, and this is what this course provides: a strong emotional engagement by lots of hands on labs and stories from real life, all to substantially improve code hygiene. Mistakes, consequences, and best practices are our blood, sweat and tears.\n\nAll this is put in the context of C and C++, and extended by core programming issues, discussing security pitfalls of these languages.\n\nSo that you are prepared for the forces of the dark side.\n\nSo that nothing unexpected happens.\n\nNothing.","skill_level":"Intermediate","version":"1.0","duration":{"unit":"d","value":3,"formatted":"3 days"},"pricelist":{"List Price":{"SI":{"country":"SI","currency":"EUR","taxrate":20,"price":2250},"DE":{"country":"DE","currency":"EUR","taxrate":19,"price":2250},"AT":{"country":"AT","currency":"EUR","taxrate":20,"price":2250},"GB":{"country":"GB","currency":"EUR","taxrate":20,"price":2250},"IT":{"country":"IT","currency":"EUR","taxrate":20,"price":2250},"NL":{"country":"NL","currency":"EUR","taxrate":21,"price":2250},"BE":{"country":"BE","currency":"EUR","taxrate":21,"price":2250},"FR":{"country":"FR","currency":"EUR","taxrate":19.6,"price":2250},"MK":{"country":"MK","currency":"EUR","taxrate":null,"price":2250},"GR":{"country":"GR","currency":"EUR","taxrate":null,"price":2250},"HU":{"country":"HU","currency":"EUR","taxrate":20,"price":2250}}},"lastchanged":"2026-01-12T11:39:44+01:00","parenturl":"https:\/\/portal.flane.ch\/swisscom\/en\/json-courses","nexturl_course_schedule":"https:\/\/portal.flane.ch\/swisscom\/en\/json-course-schedule\/24031","source_lang":"en","source":"https:\/\/portal.flane.ch\/swisscom\/en\/json-course\/cydrill-secc-ccpp"}}