`EVP_CIPHER_CTX_get_iv_length()` reports `16` for AES-ECB with `symcryptprovider`
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 68/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- c
- 领域
- cryptography, security
调研方向
从 SymCrypt-OpenSSL 中的 AES cipher provider 实现开始,并使用随 OpenSSL 3 提供的 Plain C Reproducer。将 AES-ECB 的已初始化 context IV 长度与 cipher 级别的值和 default provider 进行比较。当 symcryptprovider 对 EVP_CIPHER_get_iv_length() 和 EVP_CIPHER_CTX_get_iv_length() 均报告 0 时,即表示完成。
由索引模型根据 Issue 内容生成。
描述
Summary
When using SymCrypt-OpenSSL’s OpenSSL 3 provider (symcryptprovider), an initialized AES-ECB cipher context reports an IV length of 16 via EVP_CIPHER_CTX_get_iv_length().
ECB mode does not use an IV, so the expected context IV length is 0. OpenSSL’s default/FIPS providers report 0 for AES-ECB. The SymCrypt-OpenSSL provider appears to report the AES block size or a generic AES context IV buffer length instead.
This looks like an OpenSSL provider metadata compatibility issue in SymCrypt-OpenSSL, not an issue in the core SymCrypt primitive.
Environment
Observed on Azure Linux 3 with:
- OpenSSL:
3.3.5 - Provider module:
symcryptprovider.so - SymCrypt provider version:
1.9.5 - Provider path: ossl-modules
Expected Behavior
For AES-ECB:
EVP_CIPHER_get_iv_length(cipher) == 0
EVP_CIPHER_CTX_get_iv_length(ctx) == 0
ECB has no IV, so both cipher-level and initialized-context-level IV length should be zero.
Actual Behavior
With symcryptprovider:
EVP_CIPHER_get_iv_length(cipher) == 0
EVP_CIPHER_CTX_get_iv_length(ctx) == 16
The cipher-level metadata is correct, but the initialized context reports 16.
Why This Matters
This can break applications or test suites that use OpenSSL EVP metadata to validate cipher parameters. Even if AES-ECB encryption/decryption itself works correctly, the context metadata is inconsistent with OpenSSL provider behavior and with ECB semantics.
This may cause callers to incorrectly believe AES-ECB requires or has an IV after initialization.
Plain C Reproducer
#include <openssl/evp.h>
#include <openssl/provider.h>
#include <stdio.h>
#include <string.h>
static int test_provider(const char *provider_name)
{
int ret = 1;
OSSL_LIB_CTX *libctx = NULL;
OSSL_PROVIDER *provider = NULL;
EVP_CIPHER *cipher = NULL;
EVP_CIPHER_CTX *ctx = NULL;
unsigned char key[16];
memset(key, 0, sizeof(key));
libctx = OSSL_LIB_CTX_new();
if (libctx == NULL) {
fprintf(stderr, "OSSL_LIB_CTX_new failed\n");
goto cleanup;
}
provider = OSSL_PROVIDER_load(libctx, provider_name);
if (provider == NULL) {
fprintf(stderr, "OSSL_PROVIDER_load(%s) failed\n", provider_name);
goto cleanup;
}
cipher = EVP_CIPHER_fetch(libctx, "AES-128-ECB", NULL);
if (cipher == NULL) {
fprintf(stderr, "EVP_CIPHER_fetch(AES-128-ECB) failed for provider %s\n", provider_name);
goto cleanup;
}
ctx = EVP_CIPHER_CTX_new();
if (ctx == NULL) {
fprintf(stderr, "EVP_CIPHER_CTX_new failed\n");
goto cleanup;
}
if (EVP_CipherInit_ex2(ctx, cipher, key, NULL, 1, NULL) != 1) {
fprintf(stderr, "EVP_CipherInit_ex2 failed for provider %s\n", provider_name);
goto cleanup;
}
printf("provider: %s\n", provider_name);
printf("EVP_CIPHER_get0_name: %s\n", EVP_CIPHER_get0_name(cipher));
printf("EVP_CIPHER_get_iv_length: %d\n", EVP_CIPHER_get_iv_length(cipher));
printf("EVP_CIPHER_CTX_get_iv_length: %d\n", EVP_CIPHER_CTX_get_iv_length(ctx));
printf("\n");
ret = 0;
cleanup:
EVP_CIPHER_CTX_free(ctx);
EVP_CIPHER_free(cipher);
OSSL_PROVIDER_unload(provider);
OSSL_LIB_CTX_free(libctx);
return ret;
}
int main(void)
{
int ret = 0;
ret |= test_provider("default");
ret |= test_provider("symcryptprovider");
return ret;
}
Build
cc -Wall -Wextra -o aes_ecb_ivlen_repro aes_ecb_ivlen_repro.c -lcrypto
Run
If the provider is not in OpenSSL’s default module path:
OPENSSL_MODULES=/usr/lib64/ossl-modules ./aes_ecb_ivlen_repro
Otherwise:
./aes_ecb_ivlen_repro
Observed Output
Example output:
provider: default
EVP_CIPHER_get0_name: AES-128-ECB
EVP_CIPHER_get_iv_length: 0
EVP_CIPHER_CTX_get_iv_length: 0
provider: symcryptprovider
EVP_CIPHER_get0_name: AES-128-ECB
EVP_CIPHER_get_iv_length: 0
EVP_CIPHER_CTX_get_iv_length: 16
Suggested Fix
In SymCrypt-OpenSSL’s AES cipher provider implementation, ensure the context IV length returned for ECB mode is 0.
The provider likely needs to special-case ECB when returning the cipher context IV length, rather than returning the AES block size or a generic AES IV buffer size.
- 主要语言
- C
- 星标
- 81
- 派生
- 16
- 平均合并
- 22 小时 34 分钟
- 30 天内合并 PR
- 2
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/SymCrypt-OpenSSL 的其他 Issue
-
requests with cipher(DHE-RSA-AES256-GCM-SHA384) fail with internal error可能重新可做 @mamckee 于 341 天前认领,目前没有进行中的 PR。 未关闭investigate
microsoft/SymCrypt-OpenSSL#151 · 1 条评论 · 已指派 1 人 ·
-
难度 4/5 3-5 天 新手友好度 38/100
microsoft/SymCrypt-OpenSSL#114 · 2 条评论 ·
查看 microsoft/SymCrypt-OpenSSL 的全部 Issue
相似的 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
HarbourMasters/Shipwright#7320 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
FujiNetWIFI/fujinet-firmware#1834 ·
维护者通常 1 天内回复
-
Bug Status: Needs Triage
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
yanet-platform/yanet2#2874 ·
维护者通常 1 天内回复