Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

ID

Project

Category

View Status

Date Submitted

Last Update

0007379

SECURITY

TSS&TP

public

04-02-2016 13:57

05-02-2016 14:06

Reporter

Peter Felber

Assigned To

Peter Felber

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

assigned

Resolution

open

Platform

OS

OS Version

Product Version

Test_Spec_TS103096_V121

Target Version

Test_Spec_TS103096_V121

Fixed in Version

Summary

0007379: Check presence of Headerfield encryption_parameter in CAM

Description

For chapter 5.3.2.3:

Summary: Check that IUT discards a secured CAM containing a headerfield of type encryption_parameter.
Reference: ETSI TS 103 097 [1], clause 7.1
PICS Selection: PICS_GN_SECURITY

with {
  the IUT being in the 'authorized' state
}
ensure that {
  when {
    the IUT is receiving a SecuredMessage (CAM)
      containing header_fields[0].type
        indicating 'signer_info'
      and containing header_fields[1].type
        indicating 'generation_time'
      and containing header_fields[2] {
        containing type
          indicating 'its_aid'
        containing its_aid
          indicating 'AID_CAM'
      }
      and containing header_fields[3] {
        containing type 'encryption_parameter'
  } then {
    the IUT discards a SecuredMessage
  }
}

Tags

No tags attached.

Relationships

Notes
(0013806) Denis Filatov (administrator) 05-02-2016 12:53	I think it is necessary to provide valid enc_params to be sure that message has been rejected because of presence of the header field but not by the invalid parameters. Peter, could you please provide ones?

(0013807) Denis Filatov (administrator) 05-02-2016 12:54	I think it is necessary to provide valid enc_params to be sure that message has been rejected because of presence of the header field but not by the invalid parameters. Peter, could you please provide ones?

(0013808) Denis Filatov (administrator) 05-02-2016 12:57	It is required also for DENM and for recipient_info.

(0013812) Denis Filatov (administrator) 05-02-2016 14:06	info 0007379 3 variants for each type of messages A /branches/STF507/requality/TS103096/root/Requirements/SEC_ITSS/SEC_ITSS_RCV/SEC_ITSS_RCV_CAM/SEC_ITSS_RCV_CAM_04/TP_SEC_ITSS_RCV_CAM_04_13_BO.json [^] A /branches/STF507/requality/TS103096/root/Requirements/SEC_ITSS/SEC_ITSS_RCV/SEC_ITSS_RCV_DENM/SEC_ITSS_RCV_DENM_04/TP_SEC_ITSS_RCV_DENM_04_13_BO.json [^] U /branches/STF507/requality/TS103096/root/Requirements/SEC_ITSS/SEC_ITSS_RCV/SEC_ITSS_RCV_GENMSG/SEC_ITSS_RCV_GENMSG_04/TP_SEC_ITSS_RCV_GENMSG_04_13_BV.json [^]

Issue History
Date Modified	Username	Field	Change
04-02-2016 13:57	Peter Felber	New Issue
04-02-2016 13:57	Peter Felber	Status	new => assigned
04-02-2016 13:57	Peter Felber	Assigned To	=> Denis Filatov
05-02-2016 12:53	Denis Filatov	Note Added: 0013806
05-02-2016 12:54	Denis Filatov	Note Added: 0013807
05-02-2016 12:54	Denis Filatov	Assigned To	Denis Filatov => Peter Felber
05-02-2016 12:54	Denis Filatov	Status	assigned => new
05-02-2016 12:54	Denis Filatov	Status	new => assigned
05-02-2016 12:57	Denis Filatov	Note Added: 0013808
05-02-2016 14:06	Denis Filatov	Checkin
05-02-2016 14:06	Denis Filatov	Note Added: 0013812

MantisBT 1.2.14 [^]

Copyright © 2000 - 2024 MantisBT Team