CVE-Factory Web logic environments — 248-candidate archive
Private archive of all 248 screened CVE-Factory Web logic candidates found in YiCloud Harbor. These are archived existing images, with their original Dockerfiles and complete source/build contexts. No main vulnerability image was rebuilt for this export.
The package contains 248 main images + 31 deduplicated dependency images, totalling 100.37 GiB compressed image archives. All main archive image-config digests match the immutable Harbor references recorded in the manifests. The images target Linux amd64.
Download and run
Authenticate to Hugging Face using an account granted access, then download the full repository:
hf download --repo-type dataset pursu1ng/cvefactory-web-logic-self-contained --local-dir cvefactory-web-logic
cd cvefactory-web-logic
python3 tools/manage.py verify
python3 tools/manage.py up CVE-2023-3230
python3 tools/manage.py status CVE-2023-3230
python3 tools/manage.py exec CVE-2023-3230 --command /bin/sh
python3 tools/manage.py down CVE-2023-3230 --reset
Runtime prerequisites: Linux amd64, Docker Engine with Compose v2, Python 3.9+, and zstd. No Python third-party packages are required by the loader. Allow space for image decompression and runtime volumes. up checks archive hashes, loads and tags images by their recorded immutable config/manifest digests, extracts the full source context into .runtime/CVE-ID/source, and starts Compose with --pull never --no-build. A custom runtime directory can be set with --work-dir /your/path/CVE-ID on every command. down preserves named volumes unless --reset is supplied.
Compose publishes main-service ports to dynamically assigned localhost ports; status displays them. Services share project-scoped internal bridge networks, with external network access disabled. Proxy variables baked into original images are overridden. Database and application credentials are upstream synthetic test fixtures. Docker logs are bounded. The Docker daemon must have address pools that do not overlap the host or cluster networks.
Meaning of self-contained
All images and Compose runtime dependency images are included, along with relative bind-mount inputs and source/build contexts. Offline image loading and server/API startup require no registry credentials or downloads. Original Dockerfiles are preserved for provenance; rebuilding them may require internet access and upstream package repositories. Some upstream browser interfaces reference CDN assets or optional external integrations; those are not certified for full offline browser operation. Runtime smoke checks do not validate every browser workflow.
Validation and scope
- Static packaging: 248/248 main image config digests match Harbor; all 248 Compose definitions validate; complete dependency image mapping is included.
- Offline runtime startup checks were completed for the original pilot subset: 20/20 passed. The other 228 environments have static packaging checks only. See runtime smoke receipts, package validation, and known runtime limitations. Saleor’s storefront lacks its webpack manifest; Discourse’s HTML homepage returns 500. Their checks use the available GraphQL/JSON API endpoints. No full-browser completeness is claimed.
- This is an environment archive dataset. Tencent Harbor task delivery, Oracle=1/NOP=0, HY latest 8 rollouts, Deepseek-V4.1-Flash 5 rollouts, ATIF trajectories, hint reruns, and difficulty thresholds have not been evaluated for this export. Historical Factory verification and source screening are not substitutes for those checks.
Layout
| Path | Content |
|---|---|
metadata/environments.jsonl |
One row per CVE, product, logic mechanism, manifest location and provenance |
metadata/images.jsonl |
All 279 unique archived images, SHA256, byte size, image ID and source references |
metadata/package_validation.json |
Packaging checks and validation scope |
metadata/runtime_smoke.json |
Per-environment offline startup outcomes |
metadata/runtime_notes.json |
Known upstream runtime limitations and API readiness endpoints |
validation/startup/ |
Per-environment startup and bounded service logs |
environments/CVE-ID/Dockerfile |
Original main Dockerfile |
environments/CVE-ID/compose.original.yaml |
Original upstream Compose |
environments/CVE-ID/compose.yaml |
Portable offline Compose, using archived image tags |
environments/CVE-ID/context.tar.zst |
Complete source/build context, including task-deps, tests and original solution when present |
environments/CVE-ID/manifest.json |
Environment-to-image mapping and source provenance |
images/main/, images/dependencies/ |
Docker-save archives compressed with zstd |
tools/manage.py |
List, verify, load, up, status, logs, exec and down helper |
SHA256SUMS |
SHA256 checksums of every payload file except this checksum file itself |
Archived candidate environments
| CVE | Product | Reviewed logic issue |
|---|---|---|
| CVE-2012-1123 | ||
| CVE-2012-4456 | OpenStack Keystone | 管理 API 缺少 X-Auth-Token 校验;tests 使用 http.client 请求服务/用户角色接口,上一轮漏识别该客户端。现有断言主要为 401,需增加实际管理操作及数据断言。 |
| CVE-2012-4457 | ||
| CVE-2013-7137 | ||
| CVE-2014-0121 | ||
| CVE-2014-2066 | ||
| CVE-2014-9753 | ATutor | 确认流程对缺失/无效确认码的校验不足;源测试通过 HTTP 检查登录跳转。需补充实际身份/会话断言。 |
| CVE-2015-10057 | ||
| CVE-2015-10129 | ||
| CVE-2015-5059 | ||
| CVE-2015-8537 | ||
| CVE-2016-5835 | WordPress | 低权限 Subscriber/Contributor 可读取不应可见的文章修订历史;HTTP 测试检查修订 diff 和页面内容。 |
| CVE-2016-8870 | ||
| CVE-2016-9125 | ||
| CVE-2016-9285 | ||
| CVE-2016-9286 | ||
| CVE-2017-1001000 | ||
| CVE-2017-12850 | ||
| CVE-2017-12851 | ||
| CVE-2017-15053 | ||
| CVE-2017-15055 | ||
| CVE-2017-15195 | ||
| CVE-2017-15196 | ||
| CVE-2017-15197 | ||
| CVE-2017-15198 | ||
| CVE-2017-15199 | ||
| CVE-2017-15201 | ||
| CVE-2017-15203 | ||
| CVE-2017-15204 | ||
| CVE-2017-15205 | ||
| CVE-2017-15206 | ||
| CVE-2017-15207 | ||
| CVE-2017-15208 | ||
| CVE-2017-15209 | ||
| CVE-2017-15210 | ||
| CVE-2017-15211 | ||
| CVE-2017-15212 | Kanboard | project_id 与 tag_id 归属未共同校验,跨项目读取标签名称;HTTP 测试检查不应泄露的标签内容。 |
| CVE-2017-16754 | Bolt CMS | 未登录访问调试 profiler 路由,缺少后台身份限制;现有测试以 404/内容不可见判定,需补充管理员正常访问对照。 |
| CVE-2017-2604 | ||
| CVE-2017-5594 | ||
| CVE-2017-8342 | Radicale | 认证失败没有节流,可连续尝试口令;HTTP 测试仅检查平均响应延迟,属于身份防滥用方向,难度及计时稳定性需另评。 |
| CVE-2017-9378 | ||
| CVE-2018-12642 | ||
| CVE-2018-16886 | ||
| CVE-2018-17552 | ||
| CVE-2019-12105 | Supervisor | 管理 HTTP/XML-RPC 接口缺少认证,可访问日志和进程控制;urllib/XML-RPC 客户端导致上一轮漏筛。属于配置型鉴权,交付难度可能不足。 |
| CVE-2019-12742 | ||
| CVE-2019-12794 | ||
| CVE-2019-13240 | GLPI | 密码重置后令牌及时间戳状态未正确失效,可重复使用;测试混合 HTTP、数据库状态和源码检查,交付时须审计判分方式。 |
| CVE-2019-16766 | wagtail-2fa | 仅通过密码验证、尚未完成 2FA 的用户可访问设备管理入口;HTTP 测试覆盖新设备和二维码入口,部分断言接受 500,须加强业务效果判定。 |
| CVE-2020-11020 | ||
| CVE-2020-14213 | ||
| CVE-2020-15126 | ||
| CVE-2020-15149 | ||
| CVE-2020-15245 | ||
| CVE-2020-15270 | ||
| CVE-2020-25781 | ||
| CVE-2020-26212 | ||
| CVE-2020-26214 | ||
| CVE-2020-28036 | ||
| CVE-2020-29006 | ||
| CVE-2020-36569 | ||
| CVE-2020-5275 | ||
| CVE-2020-5300 | ||
| CVE-2020-7964 | Saleor | GraphQL 结账对象可以关联到其他用户或从其他用户解绑;源测试检查跨用户结账对象和隐私数据。 |
| CVE-2020-9381 | Total.js CMS | 后台操作缺少授权检查;源测试主要用 HTTP 状态码判断,需补充业务副作用断言。 |
| CVE-2021-21255 | ||
| CVE-2021-21324 | ||
| CVE-2021-21403 | ||
| CVE-2021-25957 | ||
| CVE-2021-25961 | SuiteCRM | 密码重置令牌与用户生命周期绑定失效;源测试覆盖删除用户后旧令牌仍被接受的情形。 |
| CVE-2021-25973 | ||
| CVE-2021-27582 | ||
| CVE-2021-29437 | ||
| CVE-2021-31606 | ||
| CVE-2021-32637 | ||
| CVE-2021-38698 | ||
| CVE-2021-38725 | ||
| CVE-2021-3992 | ||
| CVE-2021-4089 | ||
| CVE-2021-41111 | ||
| CVE-2021-41129 | ||
| CVE-2021-41191 | ||
| CVE-2021-41265 | ||
| CVE-2021-41317 | XSS Hunter Express | 认证中间件精确匹配路径,追加路径段后漏鉴权;产品名 XSS 导致误归 XSS。Factory 测试启动器调用原 app.js,以普通 HTTP 替换 TLS;仍需核对返回数据的实际敏感性。 |
| CVE-2021-42192 | ||
| CVE-2021-42235 | ||
| CVE-2021-4236 | ||
| CVE-2021-4240 | ||
| CVE-2021-43835 | Sulu CMS | 个人资料更新接受 userRoles/userGroups 等特权字段,导致批量字段赋值越权;HTTP 请求后检查实际角色集合。 |
| CVE-2021-45379 | ||
| CVE-2022-0133 | ||
| CVE-2022-0178 | ||
| CVE-2022-0179 | ||
| CVE-2022-0266 | Live Helper Chat | 拥有一般删除权限的操作员可删除受保护的主管理员或管理员组;HTTP 测试在操作后核对受保护账户/组是否仍存在。 |
| CVE-2022-0273 | ||
| CVE-2022-0579 | ||
| CVE-2022-0611 | ||
| CVE-2022-0664 | ||
| CVE-2022-0731 | ||
| CVE-2022-0824 | ||
| CVE-2022-0829 | ||
| CVE-2022-0932 | Saleor | 只有用户管理权限的员工可读取订单信息;源测试检查 GraphQL 返回是否泄露订单数据。 |
| CVE-2022-1176 | ||
| CVE-2022-1332 | ||
| CVE-2022-1397 | Easy!Appointments | Provider/Secretary 等低权限账户能调用管理员管理 API;源测试包含创建管理员、读取设置等 HTTP 请求。 |
| CVE-2022-1511 | ||
| CVE-2022-1530 | ||
| CVE-2022-1631 | ||
| CVE-2022-1715 | ||
| CVE-2022-1808 | ||
| CVE-2022-1849 | ||
| CVE-2022-1947 | ||
| CVE-2022-21684 | Discourse | 通过领取邀请绕过用户审批流程,未批准用户获得登录状态;源测试检查会话和 current_user。 |
| CVE-2022-21953 | ||
| CVE-2022-22107 | ||
| CVE-2022-2306 | ||
| CVE-2022-23510 | Cube.js | sql-runner 接口绕过租户行级数据范围;Factory 使用真实 Cube.js 0.31.23 包和测试 schema。现有判定主要检查接口移除为 404,需补跨租户数据断言。 |
| CVE-2022-23650 | ||
| CVE-2022-24781 | ||
| CVE-2022-24829 | ||
| CVE-2022-24857 | ||
| CVE-2022-25318 | ||
| CVE-2022-2583 | ||
| CVE-2022-25896 | ||
| CVE-2022-2631 | ||
| CVE-2022-26563 | ||
| CVE-2022-27157 | ||
| CVE-2022-27245 | MISP | 仅允许 CLI 修改的安全设置可经 Web API 修改,违反管理通道权限约束;测试主要检查 405,需补配置实际状态。 |
| CVE-2022-2824 | ||
| CVE-2022-2888 | ||
| CVE-2022-2997 | ||
| CVE-2022-31888 | ||
| CVE-2022-39222 | Dex | OIDC approval 请求未绑定 HMAC,其他会话可抢先获取授权码;HTTP 测试覆盖缺失/错误 HMAC、轮询和并发,需复核完整授权码消费链。 |
| CVE-2022-39263 | ||
| CVE-2022-4006 | ||
| CVE-2022-4366 | ||
| CVE-2022-46177 | ||
| CVE-2022-4686 | ||
| CVE-2022-4689 | Memos | PATCH 请求体 ID 覆盖已鉴权的目标,允许跨用户改密/改昵称;测试验证受害者密码登录和昵称。与 Memos 对象删除类 CVE 分开,后续仍须按根因去重。 |
| CVE-2022-4800 | ||
| CVE-2022-4801 | ||
| CVE-2022-4802 | ||
| CVE-2022-4806 | Memos | 跨用户删除 shortcut/resource 或覆盖 memo 作者;测试使用两个用户会话并检查 creatorId。与既有 CVE-2022-4813 的场景重叠,计入 CVE 候选但交付选题须去重。 |
| CVE-2022-4807 | ||
| CVE-2022-4808 | ||
| CVE-2022-4809 | ||
| CVE-2022-4810 | ||
| CVE-2022-4811 | ||
| CVE-2022-4813 | Memos | 通过他人资源 ID 修改/删除 shortcut 等对象;源测试同时检查响应及对象是否仍存在。 |
| CVE-2022-4814 | ||
| CVE-2022-4863 | ||
| CVE-2022-4868 | ||
| CVE-2023-0227 | ||
| CVE-2023-0609 | Wallabag | 导出接口可读取其他用户的文章,多种导出格式共享越权路径。 |
| CVE-2023-0610 | Wallabag | 通过注释 ID 跨用户修改、删除或读取注释;源测试使用两个用户的 HTTP 会话。 |
| CVE-2023-0678 | ||
| CVE-2023-0734 | ||
| CVE-2023-0914 | ||
| CVE-2023-1307 | ||
| CVE-2023-1463 | ||
| CVE-2023-1537 | Answer | 验证码校验后未消费,可重复用于注册等请求;HTTP 测试检查第二次提交的验证码错误。Factory 构建脚本把验证码答案固定为测试值,须移除测试便利性造成的难度干扰后再评估。 |
| CVE-2023-1543 | ||
| CVE-2023-2104 | ||
| CVE-2023-2105 | ||
| CVE-2023-2183 | ||
| CVE-2023-2202 | ||
| CVE-2023-2227 | ||
| CVE-2023-22453 | ||
| CVE-2023-23929 | ||
| CVE-2023-27583 | ||
| CVE-2023-29019 | ||
| CVE-2023-2943 | ||
| CVE-2023-31123 | ||
| CVE-2023-31287 | ||
| CVE-2023-32077 | ||
| CVE-2023-32078 | ||
| CVE-2023-3230 | FOSSBilling | 待开通、暂停或取消的订单仍可下载付费内容;源测试分别覆盖三个不应允许下载的订单状态。 |
| CVE-2023-3394 | ||
| CVE-2023-33968 | ||
| CVE-2023-33970 | ||
| CVE-2023-3574 | Pimcore CMF | 没有 CMF 权限的后台用户仍可读取自动化规则;HTTP 测试对照有权限/无权限会话,CSRF 字样属于测试上下文,核心机制为角色授权。 |
| CVE-2023-3700 | Easy!Appointments | Provider 可通过操纵目标人员 ID 为其他人员创建不可预约时间,违反日程归属约束。 |
| CVE-2023-37265 | ||
| CVE-2023-37904 | Discourse | 单次邀请可被并发领取,创建多个用户;源测试核对并发后实际创建用户数。 |
| CVE-2023-40027 | ||
| CVE-2023-40174 | social-media-skeleton | 会话到期后仍可访问主页、资料和设置;测试覆盖过期 Cookie 重放,多用 302/200 判定,需检查实际身份失效。 |
| CVE-2023-40570 | ||
| CVE-2023-40585 | Metal3 Ironic image | 设置 htpasswd 后 API 启动配置未正确启用 Basic Auth,敏感管理接口仍可无认证访问;源测试以 HTTP 401 为主。 |
| CVE-2023-41058 | ||
| CVE-2023-4106 | ||
| CVE-2023-4198 | ||
| CVE-2023-43664 | ||
| CVE-2023-43805 | Nexkey | 队列管理面板的 URL 编码与鉴权路径匹配不一致,导致绕过认证;使用 http.client 保留编码路径,上一轮漏识别。需补实际队列数据/操作效果。 |
| CVE-2023-44394 | ||
| CVE-2023-44400 | Uptime Kuma | 修改密码后旧身份令牌仍可登录;测试包含 WebSocket 身份验证和被窃令牌复用场景。 |
| CVE-2023-45659 | ||
| CVE-2023-46241 | ||
| CVE-2023-4650 | ||
| CVE-2023-4697 | ||
| CVE-2023-49804 | Uptime Kuma | 修改密码未断开其他已登录 Socket.IO 会话;源测试检查多会话连接及断开/刷新事件,需补旧会话确实不能操作监控对象的断言。 |
| CVE-2023-51386 | ||
| CVE-2023-51442 | ||
| CVE-2023-5838 | ||
| CVE-2023-5976 | ||
| CVE-2024-0551 | AnythingLLM | default 角色可调用管理数据导出接口;角色授权问题,不能误写成无需登录。 |
| CVE-2024-0795 | ||
| CVE-2024-0798 | ||
| CVE-2024-10366 | ||
| CVE-2024-13060 | ||
| CVE-2024-2035 | ||
| CVE-2024-21665 | ||
| CVE-2024-21667 | ||
| CVE-2024-2217 | ||
| CVE-2024-2260 | ||
| CVE-2024-23637 | ||
| CVE-2024-24573 | ||
| CVE-2024-24748 | Discourse | 父分类 has_children 泄露用户无权查看的秘密子分类存在性;属于对象可见性边界,影响较小,单独标注,不等同读取隐藏内容。 |
| CVE-2024-24819 | ||
| CVE-2024-24822 | Pimcore | 缺少 tags_configuration 权限仍能调用标签创建/删除接口;HTTP 测试检查 success 返回和拒绝结果,需补对象最终状态。 |
| CVE-2024-25108 | Pixelfed | 仅授予 read scope 的 OAuth 令牌可调用管理员 API;账户角色与令牌授权范围未共同校验。 |
| CVE-2024-25977 | ||
| CVE-2024-2702 | ||
| CVE-2024-27937 | GLPI | 通过 actor 下拉框请求中的实体条件读取无权访问实体的用户信息;HTTP 测试核对其他实体的邮箱内容。属于跨实体隔离失效,不是单纯登录名存在性枚举。 |
| CVE-2024-28000 | ||
| CVE-2024-29885 | ||
| CVE-2024-31218 | Webhood | 新实例未建立管理员时,无认证请求可创建管理员并获得管理 API 访问;源测试覆盖创建、登录及 API 调用。需复核初始化前提和测试间状态隔离。 |
| CVE-2024-31453 | PsiTransfer | 分享桶完成后缺少写入约束,知道分享 ID 的访问者可追加文件;HTTP 测试覆盖创建、追加、锁定和原文件保留。原始测试还涉及单文件完成态,交付应与 CVE-2024-31454 区分。 |
| CVE-2024-3150 | ||
| CVE-2024-3283 | AnythingLLM | Manager 可赋值内部 multi_user_mode 设置,重新打开初始化路径;测试核对实际模式状态和权限提升路径。 |
| CVE-2024-34077 | MantisBT | 密码重置过程未验证请求者持有邮箱确认哈希;源测试通过 HTTP 尝试更改密码并检查数据库密码哈希。 |
| CVE-2024-34695 | WOWS Karma | 并发创建请求绕过同一作者对同一对象的 24 小时冷却限制;源测试包含并发和分批请求。 |
| CVE-2024-34709 | Directus | 登出后旧会话令牌仍可访问受保护 API;源测试覆盖重复使用及不同接口。 |
| CVE-2024-35184 | ||
| CVE-2024-36399 | Kanboard | URL project_id 用于权限检查,POST project_id 用于实际操作,导致跨项目添加成员;测试核对成员实际权限。 |
| CVE-2024-37312 | Nextcloud user_oidc | 管理员关闭 ID4me 后登录/回调 GET 入口仍可用,开关状态未正确限制认证流程;测试检查入口被拒绝及表单不可见,需验证完整认证链。 |
| CVE-2024-37889 | MyFinances | 修改发票 ID 可查看其他用户的发票及敏感字段;源测试检查跨用户 HTTP 访问和数据泄露。 |
| CVE-2024-39313 | ||
| CVE-2024-40627 | ||
| CVE-2024-4146 | ||
| CVE-2024-4154 | ||
| CVE-2024-46506 | ||
| CVE-2024-47183 | Parse Server | 开启 allowCustomObjectId 后,新用户自定义 ID 可与 role: 命名空间冲突,获得角色权限;源测试包含创建身份和访问/修改受角色保护的数据。 |
| CVE-2024-4819 | ||
| CVE-2024-5129 | Lunary | 跨项目删除他人的数据集,缺少对象归属验证;源测试核对目标数据集是否实际被删除。 |
| CVE-2024-51378 | ||
| CVE-2024-8005 | ||
| CVE-2025-49591 |
Provenance and licensing
Source: upstream CVE-Factory task contexts, corresponding existing cvefactory Harbor artifacts, and their original public dependency images. Each environment manifest records the upstream split and immutable Harbor artifact reference. Original license files remain in the contexts/images; the components retain their respective licenses. This package makes no blanket relicensing claim.
- Downloads last month
- 50