Like to report a debug build error, hopefully you can solve this, its a bit unhandy to develop an application when you're not able to build it for debugging,

Using cryptopp version 8.9 with Visual Studio 2022 in a MFC application.

When I build this piece of  code in debug mode:

> void SomeClass::EncryptString(CString& str) 
> {
> 
> 	AutoSeededRandomPool rng;
> 	
> 	// Generate private key
> 	RSA::PrivateKey privateKey;
> 	privateKey.GenerateRandomWithKeySize(rng, 2048);
> 	RSA::PublicKey publicKey(privateKey);
> 
> 	std::string plain = CW2A(str), cipher, recovered;
> 
> 	// Encryption
> 	RSAES_OAEP_SHA_Encryptor e(publicKey);
> 
> 	StringSource ss1(plain, true,
> 		new PK_EncryptorFilter(rng, e,
> 			new StringSink(cipher)
> 			) // PK_EncryptorFilter
> 		); // StringSource
> }

When executing line: **privateKey.GenerateRandomWithKeySize(rng, 2048);** I got the following debug message:

Unhandled exception at 0x00007FF73F1F31FC An invalid parameter was passed to a function that considers invalid parameters fatal.

And Visual Studio 2022 is showing:

> extern "C" __declspec(noreturn) void __cdecl _invoke_watson(
>         wchar_t const* const expression,
>         wchar_t const* const function_name,
>         wchar_t const* const file_name,
>         unsigned int   const line_number,
>         uintptr_t      const reserved
>         )
>     {
>         UNREFERENCED_PARAMETER(expression   );
>         UNREFERENCED_PARAMETER(function_name);
>         UNREFERENCED_PARAMETER(file_name    );
>         UNREFERENCED_PARAMETER(line_number  );
>         UNREFERENCED_PARAMETER(reserved     );
>     
>         if (IsProcessorFeaturePresent(PF_FASTFAIL_AVAILABLE))
>         {
>             __fastfail(FAST_FAIL_INVALID_ARG);
>         }
>     
>         // Otherwise, raise a fast-fail exception and termintae the process:
>         __acrt_call_reportfault(
>             _CRT_DEBUGGER_INVALIDPARAMETER,
>             STATUS_INVALID_CRUNTIME_PARAMETER,
>             EXCEPTION_NONCONTINUABLE);
>     
>         TerminateProcess(GetCurrentProcess(), STATUS_INVALID_CRUNTIME_PARAMETER);
>     }

And stop at: **__fastfail(FAST_FAIL_INVALID_ARG);**.

While the same piece of code when building in release mode is working just fine.

I use the debug version of cryptlib.lib for building in debug mode and the release version for building in release mode.
An invalid parameter was passed to a function that considers invalid parameters fatal. Only when building in debug mode.
This is a GitHub Issue
repo:cryptopp
owner:weidai11
Title : An invalid parameter was passed to a function that considers invalid parameters fatal. Only when building in debug mode.
Issue date:

--- start body ---
Like to report a debug build error, hopefully you can solve this, its a bit unhandy to develop an application when you're not able to build it for debugging,

Using cryptopp version 8.9 with Visual Studio 2022 in a MFC application.

When I build this piece of  code in debug mode:

> void SomeClass::EncryptString(CString& str) 
> {
> 
> 	AutoSeededRandomPool rng;
> 	
> 	// Generate private key
> 	RSA::PrivateKey privateKey;
> 	privateKey.GenerateRandomWithKeySize(rng, 2048);
> 	RSA::PublicKey publicKey(privateKey);
> 
> 	std::string plain = CW2A(str), cipher, recovered;
> 
> 	// Encryption
> 	RSAES_OAEP_SHA_Encryptor e(publicKey);
> 
> 	StringSource ss1(plain, true,
> 		new PK_EncryptorFilter(rng, e,
> 			new StringSink(cipher)
> 			) // PK_EncryptorFilter
> 		); // StringSource
> }

When executing line: **privateKey.GenerateRandomWithKeySize(rng, 2048);** I got the following debug message:

Unhandled exception at 0x00007FF73F1F31FC An invalid parameter was passed to a function that considers invalid parameters fatal.

And Visual Studio 2022 is showing:

> extern "C" __declspec(noreturn) void __cdecl _invoke_watson(
>         wchar_t const* const expression,
>         wchar_t const* const function_name,
>         wchar_t const* const file_name,
>         unsigned int   const line_number,
>         uintptr_t      const reserved
>         )
>     {
>         UNREFERENCED_PARAMETER(expression   );
>         UNREFERENCED_PARAMETER(function_name);
>         UNREFERENCED_PARAMETER(file_name    );
>         UNREFERENCED_PARAMETER(line_number  );
>         UNREFERENCED_PARAMETER(reserved     );
>     
>         if (IsProcessorFeaturePresent(PF_FASTFAIL_AVAILABLE))
>         {
>             __fastfail(FAST_FAIL_INVALID_ARG);
>         }
>     
>         // Otherwise, raise a fast-fail exception and termintae the process:
>         __acrt_call_reportfault(
>             _CRT_DEBUGGER_INVALIDPARAMETER,
>             STATUS_INVALID_CRUNTIME_PARAMETER,
>             EXCEPTION_NONCONTINUABLE);
>     
>         TerminateProcess(GetCurrentProcess(), STATUS_INVALID_CRUNTIME_PARAMETER);
>     }

And stop at: **__fastfail(FAST_FAIL_INVALID_ARG);**.

While the same piece of code when building in release mode is working just fine.

I use the debug version of cryptlib.lib for building in debug mode and the release version for building in release mode.
--- end body ---

The issue reported is related to a debug build error in the Crypto++ library when using Visual Studio 2022. The error occurs due to an invalid parameter being passed to the function `GenerateRandomWithKeySize`, which is causing a fatal exception in debug mode. This is not a security vulnerability but rather a development issue that affects the ability to debug the application. The code works correctly in release mode, indicating that the problem is specific to the debug configuration.